Bug #36160 mysqld: my_new.cc:51: int __cxa_pure_virtual(): Assertion `"Pure virtual method
Submitted: 16 Apr 2008 21:23 Modified: 16 May 2008 23:51
Reporter: Ryan Lowe Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.27-standard-log OS:Linux (Linux 2.6.9-42.ELsmp #1 SMP x86_64 x86_64 x86_6)
Assigned to: CPU Architecture:Any

[16 Apr 2008 21:23] Ryan Lowe
Description:
mysqld: my_new.cc:51: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed.
mysqld got signal 6;
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=131072
read_buffer_size=131072
max_used_connections=234
max_connections=256
threads_connected=7
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1081470 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x2adbc00030
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=0x4830fff8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x7375003265626976
Stack trace seems successful - bottom reached
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack 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 0x2adb5113e0  is invalid pointer
thd->thread_id=17792025
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.

Number of processes running now: 0
080415 23:33:26  mysqld restarted
080415 23:33:27  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
080415 23:33:27  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 9 4164337721.

<... InnoDB crash recovery ...>

How to repeat:
Could not reproduce ... Not convinced that this was a bug, but thought that since we couldn't find hardware issues, you might want to see it:)
[16 Apr 2008 23:51] MySQL Verification Team
Thank you for the bug report. The server version you have reported is quite
older, could you please upgrade to latest released version and test. If you
still get the same behavior please comment and re-open this bug report.
Thanks in advance.
[17 May 2008 23: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".