MySQL Bugs: #39503: mysqld got signal 11;

Bug #39503	mysqld got signal 11;
Submitted:	17 Sep 2008 19:23	Modified:	17 Oct 2008 21:41
Reporter:	ben nduati	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.32-Debian_7etch6	OS:	Linux (Debian GNU/Linux 4.0 )
Assigned to:		CPU Architecture:	Any
Tags:	mysql server crash

Description:
this server is a redundant fail over slave server. It serves no requests but every so often it crashes with the following message logged in the error log file

mysqld got signal 11;
thd=0x8d175e8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xb4623078, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81c06b9
0x81b0d8d
0x81b199e
0x81b5741
0x82b7eea
0xb7ed1240
0xb7d0c49e
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stac
k trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil)  is invalid pointer
thd->thread_id=15364

How to repeat:
no threads running other than the two replication threads at time of crash

Thank you for the report.

But version 5.0.32 is old and many bugs were fixed since. Please upgrade to current version 5.0.67, try with it and if problem still exists try to provide more information: we need a query which causes the failure.

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".