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()
 
MaxDB- Driver Bug? *** glibc detected *** ..., can you help?

MaxDB- Driver Bug? *** glibc detected *** ..., can you help?

2007-04-27       - By Alexander Finke

 Back
Hi,

i i` ve the folling problem:

*** glibc detected *** /usr/sbin/httpd2-prefork: malloc(): memory corruption:
0x000055555594a620 ***

I use apache2, php5 - 5.1.2, SLES 10, UnixODBC, MaxDB 7.6 (newest) (x86_64).
This error occurs in my php- script in the
odbc_exec() function. But only on the 64- Bit System, on a 62 Bit System,
everythink is working very well.

I tried already a lot of thinks to fix this bug. In the past i expected the bug
in the unixODBC Driver Manager in combination
with the MaxDB Database drivers (libsqlod.so / libsqlodw.so), because the
unixODBC Isql Utility gave me only the first dataset back and
in the SQL-Trace more data.

BTW, this bug will be fixed in the next unixODBC Version (unixODBC-2 (See http://DBC-2.ora-code.com).2.13pre).

So i thought the bug could be in the maxdb- driver and i tried different MaxDB
drivers for different 64 Bit Versions, but with no success.
At least i checked all SharedObjects on my System for deps mistakes

(( find / -name *.so -exec ldd {} \; ) > SHARED_LIBS_DEPENDIS)

but also with no success.

I know another person who has this bug too (if it is), but he uses a different
OS (OpenSuSE) and a different PHP- Version which is
smaller than mine.

But he uses the self MaxDB Version (7.6.xx), so perhaps it s a bug in the maxdb
drivers on 64 Bit Systems?
What do you think? Perhaps somebody of you knows this error and a solution for
it?

It would be very fine if you know a short term solution or somethink like that,
because our system has to go productive the following days, but so long there
are the glibc errors, it cant`t.

Many thanks in advance for you help!

Wish you a nice day,

wbr, alexander
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ _____
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192


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