LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

lv71/labview: realloc(): invalid next size:

Linux Weenies;

I've had good luck running LV7.1 on Suse 10.1 and 10.3 (x86_64).  I have installed the box version from Novell of Suse 10.3 and now get the following errors:

*** glibc detected *** /usr/local/lv71/labview: realloc(): invalid next size: 0x223b1bf0 ***
(no debugging symbols found)
======= Backtrace: =========
/usr/local/lv71/lib/libc.so.6[0xf7bea4b6]
/usr/local/lv71/lib/libc.so.6[0xf7bed7ed]
/usr/local/lv71/lib/libc.so.6(realloc+0x10a)[0xf7bee1aa]
/usr/local/lv71/labview[0x822752d]
/usr/local/lv71/labview(DSSetHandleSize+0x69)[0x82262c9]
/usr/local/lv71/labview(FAppendName+0x60)[0x823c970]
/usr/local/lv71/labview(_Z9FListDir2PP6Path_tPP5CPStrPP10FMFileTypei+0x24f)[0x81d972f]
/usr/local/lv71/labview[0x86a5996]
/usr/local/lv71/labview[0x86a5a8e]
BTW:  I have tried placing earlier versions of glibc within /usr/ocal/lv71/lib/, it then can't find all the older x libraries etcetera.

   ...Dan


0 Kudos
Message 1 of 6
(3,693 Views)

Hi Dan,

What versions of the kernel and NI-KAL do you have?  Also, what versions of glibc have you tried to use? 

Jennifer R.
National Instruments
Applications Engineer
0 Kudos
Message 2 of 6
(3,660 Views)
The kernel is:
Linux version 2.6.22.5-31-default (geeko@buildhost) (gcc version 4.2.1 (SUSE Linux)) #1 SMP 2007/09/21 22:29:00 UTC
glibc is:
2.6.1-18 (and I've tried 2.2, 2.3, 2.4, 2.5)
NI-KAL?  How do I find out?  Just for giggles, I looked it up and downloaded it, tried to make it but it complained about my 64 bit system.  The thing is, I have had it working on my 64 bit system before the OS renewal (clean hard drive).

   ...Dan
0 Kudos
Message 3 of 6
(3,656 Views)
For what it's worth, running gdb on LabView shows an infinite loop at:
#0  0xffffe405 in __kernel_vsyscall ()
#1  0xf7c8f8d6 in __lxstat () from /lib/libc.so.6
#2  0x081d9797 in FListDir2 ()
#3  0x086a5996 in ?? ()
#4  0x086a5a8e in ?? ()
-- snip --
#4248 0x086a5a8e in ?? ()
#4249 0x086a5948 in ?? ()
#4250 0x086d6052 in OMIVIClassMgr::Init ()
#4251 0x086c0264 in ObjManagers::RegisterObjClassManager ()
#4252 0x086bfe78 in RegisterObjClassManager ()
#4253 0x086bff99 in InitObjMgr ()
#4254 0x08597a42 in InitApp ()
#4255 0x085b2146 in ?? ()
#4256 0x085b51d7 in ?? ()
#4257 0x08282835 in ?? ()
#4258 0x08282cca in WSendEvent ()
#4259 0x0822c9f4 in InitializeApp ()
#4260 0x08230a8e in ?? ()
#4261 0x08230b03 in main ()
Hopefully, someone familiar with the internals can help figure this out.
   ...Dan
0 Kudos
Message 4 of 6
(3,639 Views)
Never mind, I found the solution.  The problem appears to be with ext3 filesystems, the solution is in this thread:

http://forums.ni.com/ni/board/message?board.id=170&message.id=83794&query.id=503762#M83794

namely:

tune2fs -O "^dir_index" /dev/hda1
0 Kudos
Message 5 of 6
(3,638 Views)

Hi Dan,

NI-KAL is a low-layer driver between the Linux kernel and National Instruments software.  You can find information on the various versions under What is “an appropriate version of NI-KAL”?  However, it sounds like the version you have currently is fine. 

I'm glad to hear you've found a solution.  Thanks for sharing the information. 

Jennifer R.
National Instruments
Applications Engineer
0 Kudos
Message 6 of 6
(3,621 Views)