MySQL Bugs: #38456: mysqld cored on my_malloc+0x32 during TPCB db drop in ACRT run

Bug #38456	mysqld cored on my_malloc+0x32 during TPCB db drop in ACRT run
Submitted:	30 Jul 2008 12:27	Modified:	22 Oct 2010 10:31
Reporter:	Jonathan Miller	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	mysql-5.1-telco-6.3	OS:	Linux
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Clone revision-id: msvensson@mysql.com-20080725162754-t8vjg77gcckrk52a

key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=26
max_threads=151
threads_connected=3
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338290 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x2aaab8067aa0
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...
/data0/cr_autotest/libexec/mysqld(print_stacktrace+0x27)[0x7623c7]
/data0/cr_autotest/libexec/mysqld(handle_segfault+0x31d)[0x6242ad]
/lib64/libpthread.so.0[0x3907e0de80]
/lib64/libc.so.6[0x3907271e03]
/lib64/libc.so.6(__libc_malloc+0x7d)[0x3907272efd]
/data0/cr_autotest/libexec/mysqld(my_malloc+0x32)[0x94e312]
/data0/cr_autotest/libexec/mysqld(alloc_root+0x7e)[0x94eb0e]
/data0/cr_autotest/libexec/mysqld(_Z14open_table_defP3THDP14st_table_sharej+0xd96)[0x67f126]
/data0/cr_autotest/libexec/mysqld(_Z15get_table_shareP3THDP10TABLE_LISTPcjjPi+0x1f7)[0x66e9c7]
/data0/cr_autotest/libexec/mysqld[0x670869]
/data0/cr_autotest/libexec/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootPbj+0x78f)[0x67578f]
/data0/cr_autotest/libexec/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjj+0x3cf)[0x67685f]
/data0/cr_autotest/libexec/mysqld(_Z28open_and_lock_tables_derivedP3THDP10TABLE_LISTb+0x37)[0x676b87]
/data0/cr_autotest/libexec/mysqld(_ZN19Event_db_repository20drop_events_by_fieldEP3THD23enum_events_table_field19st_mysql_lex_string+0x76)[0x78ccf6]
/data0/cr_autotest/libexec/mysqld(_ZN6Events18drop_schema_eventsEP3THDPc+0x59)[0x78d849]
/data0/cr_autotest/libexec/mysqld(_Z11mysql_rm_dbP3THDPcbb+0x14a)[0x71d53a]
/data0/cr_autotest/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x69e4)[0x639404]
/data0/cr_autotest/libexec/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x32a)[0x63a7aa]
/data0/cr_autotest/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x3ba)[0x63ab6a]
/data0/cr_autotest/libexec/mysqld(_Z10do_commandP3THD+0xc6)[0x63bd76]
/data0/cr_autotest/libexec/mysqld(handle_one_connection+0x64c)[0x62c75c]
/lib64/libpthread.so.0[0x3907e06307]
/lib64/libc.so.6(clone+0x6d)[0x39072d1ded]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x13109bb0 = DROP DATABASE TPCB
thd->thread_id=100
thd->killed=NOT_KILLED

How to repeat:
Not sure, only happened once so far

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

1.  did you have event scheduler enabled?
2.  did you have any events defined?
3.  was the table structure for events matching the one from mysql_install_db ?

maybe it was a duplicate of this?
BUG 12394306 - THE SERVER MAY CRASH IF MYSQL.EVENT IS CORRUPTED 

"Noted in 5.1.58, 5.5.13, 5.6.3 changelogs.

The server failed to detect incorrect structure of the mysql.event
table and crashed trying to use it. "