LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

sqlite3 shared library crash in Linux labview2011 On malloc() failed

I am using Sqlite Api from http://www.labview-tools.com/software/sqlite-api/ with Labview linux 2011. I created a VI that returns the tables names from a database. The Api loads a shared library and connects with it to the database. Under Linux labview 2009 it works as it should and retrive the tables names. Under Linux Labview 2011 it doesnt work and popup Error code 7 A malloc() faild . the attached zip file contains the vi Test_Sqlite.vi and the API with the Shared library file sqlite3x32.so I working on Labview 2011 and want it to work as in Labview 2009
0 Kudos
Message 1 of 13
(3,688 Views)
The Attache File
0 Kudos
Message 2 of 13
(3,678 Views)

Uh, nothing is attached...

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 3 of 13
(3,670 Views)
For some reason I couldnt attach the zip file
0 Kudos
Message 4 of 13
(3,659 Views)
Is there another way to send the file. I can't attach it to the thread.
0 Kudos
Message 5 of 13
(3,652 Views)
0 Kudos
Message 6 of 13
(3,645 Views)

Hello, Which Linux distribution exactly are you using?

Regards

0 Kudos
Message 7 of 13
(3,628 Views)

I'm using Centos 5.5

0 Kudos
Message 8 of 13
(3,613 Views)

Have you contacted the creator of that library? He is a competent programmer and should be able to find out quickly if it is a LabVIEW version problem or something with your Linux distribution. I'm pretty sure he tested it with LabVIEW 2011 too, so changes are that it is something with CentOS that screws up.

 

And if I had a guess, I would point at some C runtime library versioning issues. Using shared libraries in LabVIEW can be a little tricky as LabVIEW has its own linkage to the C runtime library and the shared library can define a strict C runtime version dependency too. If they both end up using different versions, you can end up in a bit of a mess if you happen to pass C runtime objects (allocated memory buffers, file objects, etc.) between the different runtime libraries.

 

It could be as easy as upgrading your runtime libraries or as complicated as upgrading/recompiling your kernel with a different GCC compiler toolchain version.

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 9 of 13
(3,590 Views)

I created the library, after it failed to work with the library distributed with the sqlite Api package.<br />

On same Centos computer I have both LV2009 and LV2011.<br />

I tested the libraries on each LV version both libraryies worked with LV2009 and faild on LV2011.

0 Kudos
Message 10 of 13
(3,580 Views)