Bug #64607 "glibc detected corrupted double-linked list" during a select
Submitted: 10 Mar 2012 5:16 Modified: 1 Jul 2012 17:30
Reporter: Hernan Castro Email Updates:
Status: No Feedback Impact on me:
None 
Category:Connector / C++ Severity:S2 (Serious)
Version:5.1.49-3 OS:Linux (Debian Squeeze 6.0.3)
Assigned to: CPU Architecture:Any

[10 Mar 2012 5:16] Hernan Castro 
Description:
Hello, I have an estrange problem, my program do a simple query to verify the Identity of the users 

This code work hundred of time but tonight I receive this error 
*** glibc detected *** ./GameServer: corrupted double-linked list: 0x000000000265c758 ***

I need some help to identify the reason of this error 

How to repeat:
I need some assistance to reproduce this error
[10 Mar 2012 5:18] Hernan Castro 
Full error description

Attachment: full_error.txt (text/plain), 8.52 KiB.
[10 Mar 2012 5:21] Hernan Castro 
Class whit error

Attachment: CDb.cpp (text/x-c++src), 27.62 KiB.
[10 Mar 2012 5:23] Hernan Castro 
The error was on the getUsers Method
[19 Mar 2012 20:19] Brian Davies 
glibc traceback for similar error on Gentoo

Attachment: err (application/octet-stream, text), 10.11 KiB.
[19 Mar 2012 20:28] Brian Davies 
This looks very similar to a problem that I have just seen today on a program using ODBC/connect.  Apparently random errors where the MySQL parser mostly works just fine but occasionally reports a 1064 error with (typically control) characters that were not in the SQL command submitted.  I have captured the glibc traceback and attached it.  As indicated in the traceback the client library in use is libmysqlclient.so.16 with libmyodbc3(or5 - both exhibit the symptoms).so.3.51.29.  

The same program running on an Ubuntu 10.04LTS machine with the standard installs (5.1.56) does not appear does not appear to exhibit the symptoms.

Elwyn Davies
[1 Jun 2012 17:30] Sveta Smirnova 
Thank you for the report.

> This code work hundred of time but tonight I receive this error 

Please check memory using, for example, memtest86 utility.
[2 Jul 2012 1:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".