Bug #32716 MySQL Crashs (no strack trace)
Submitted: 26 Nov 2007 13:44 Modified: 26 Dec 2007 14:05
Reporter: Dave Juntgen Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.0.46 OS:Linux (x86_64)
Assigned to: CPU Architecture:Any
Tags: crash, no stack strace

[26 Nov 2007 13:44] Dave Juntgen
Description:
Hello,

after running for 4 days MySQL crashed.  The dump did not have a stack trace and the only bug I could find related to the error message was: http://bugs.mysql.com/bug.php?id=28561 

071126  8:07:32 - mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=3221225472
read_buffer_size=2093056
max_used_connections=57
max_connections=200
threads_connected=18
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3964126 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x11d71b80
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=0x447a5068, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
New value of fp=0x11d71b80 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 stack trace. Reso
lved
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 0x2aac944105f0  is invalid pointer
thd->thread_id=5567146
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed.
Fatal signal 6 while backtracing

Number of processes running now: 0

Thanks.

How to repeat:
I have no idea, it just happend with no reason - if there is something I could do to gather more info for you guys please let me know.
[26 Nov 2007 14:05] MySQL Verification Team
Thank you for the bug report. Could you please see the bug: http://bugs.mysql.com/bug.php?id=30201 it is related to your case.
Thanks in advance.
[27 Dec 2007 0: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".