'double free or corruption' when MySQL restarts
Hello!
RHEL 5.2, mysql 5.1.46
I am having an issue where a persistent connection fail and I see a double free when the MySQL server daemon is restarted. My application works fine up until I issue the restart. I have captured the core file and examined the data in gdb. Looking at the trace below, frame 11 seems to indicate a problem with client.c. The problem disappears if I create a new connection everytime I call my doquery() function, however this is not very efficient. Has anybody experienced an issue like this?
I cut out only what I thought would be useful, I can provide the full stack trace if needed. Thanks for your assistance!
Brian
(gdb) frame 10
#10 0x000000000044b7f1 in mysql_send_query (mysql=0x40da18b0,
query=0x40da0ea0 "SELECT * FROM TableA WHERE FieldName='user' AND Source=5", length=103) at client.c:2894
2894 in client.c
(gdb) frame 11
#11 0x000000000044b859 in mysql_real_query (mysql=0x6bad, query=0x6bb0 <Address 0x6bb0 out of bounds>, length=6)
at client.c:2905
2905 client.c: No such file or directory.
in client.c
Current language: auto; currently c
(gdb) frame 12
#12 0x0000000000427df3 in doquery (conn=0x40da18b0, lm=0x1eaa15b0,
msg=0x40da0ea0 "SELECT * FROM TableA WHERE FieldName='user' AND Source=5" maxfail=60, logfreq=10, retry=1) at doquery.cpp:19
19 while(mysql_real_query(conn,msg,strlen(msg))) {
Subject
Views
Written By
Posted
'double free or corruption' when MySQL restarts
3568
December 19, 2011 01:07PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.