Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
mysql:it 's a db not a dbms how it 's possible?!
Does the binary log enabling affect the MySQL performances?
Strange behavior, Table Level Permission
FULLTEXT query format question
Preventing Duplicate Entries
Comparing and writing out BLOBS
Executing MySQL Commands From Within C Program
Can 't access mysql after kernel upgrade
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Downgrade Mysql from 4 to 3 23
MySQL Cluster Software
mysql test 4 1 fails with the gis test
ERROR 2002: Can 't connect to local MySQL server through socket
Getting Identity after INSERT
Update one field with more fields from another table
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
mysql have same function mthod as Oracle decode()
 
libsqlod.so

libsqlod.so

2007-03-21       - By Andres Rebolledo

 Back
Hi all,

I am currently trying to upgrade from 7.6.00.12 to 7.6.00.34.  I am
having 1 problem.  I compile a C++ application using which uses
libsqlod.so.  The libsqlod from version 7.6.00.12 works fine, but the
version from 7.6.00.34 gives me a compiler warning:

/usr/lib/gcc/i586-suse-linux/4.1.0/../../../../i586-suse-linux/bin/ld:
warning: libstdc++.so.5, needed by /opt/sdb/programs/lib/libsqlod.so,
may conflict with libstdc++.so.6

This suggests the latest version of libsqlod was compiled with the old
version of libstdc++.  Plus, our application is now crashing with
segmentation faults at random times.  Here is an example from gdb:

#0  0xb7eb6428 in _int_malloc () from /lib/libc.so.6
#1  0xb7eb8206 in malloc () from /lib/libc.so.6
#2  0xb7c12a50 in sql57k_pmalloc () from /opt/sdb/programs/lib/libsqlod.so
#3  0xb7c12bb6 in sqlallocat () from /opt/sdb/programs/lib/libsqlod.so
#4  0xb7bc758b in pr03mAllocatF () from /opt/sdb/programs/lib/libsqlod.so
#5  0xb7bcfd8b in pr05IfCom_String_NewDynString () from
/opt/sdb/programs/lib/libsqlod.so
#6  0xb7b933db in paSQLConnect () from /opt/sdb/programs/lib/libsqlod.so
#7  0xb7b94dba in SQLConnect () from /opt/sdb/programs/lib/libsqlod.so
#8  0x08054123 in snDatabase::connectDB (this=0xbfdbac20) at
../src/DB/snDatabase.cpp:106
#9  0x080580b6 in snUnitDatabase::getUnitsList (this=0xbfdbac20,
list=@(protected)) at ../src/DB/snUnitDatabase.cpp:240
#10 0x08081415 in snRTDB::reloadUnitsList (this=0x81532e8,
lastUnitRefresh=@(protected)) at ../src/snRTDB.cpp:72
#11 0x0805055e in main (argc=Cannot access memory at address 0xa

I am currently testing to see if I can compile our application with the
7.6.00.12 libsqlod and run the application on the 7.6.00.34 kernel.  Is
this a valid solution?  If not, what other options do I have?

Thanks,
Andres



--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=mysql@(protected)