MySQL Bugs: #40322: MySQL Server Crash

Bug #40322	MySQL Server Crash
Submitted:	24 Oct 2008 21:11	Modified:	3 May 2009 11:50
Reporter:	Gary Pendergast	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	5.1.23-ndb-6.2.15-cluster-gpl-log	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Server crash. Here is the backtrace:

/usr/sbin/mysqld(print_stacktrace+0x1e)[0x6ef74e]
/usr/sbin/mysqld(handle_segfault+0x303)[0x5da173]
/lib64/libpthread.so.0[0x35fd80de80]
/lib64/libc.so.6(memcpy+0xa0)[0x35fc47a170]
/usr/sbin/mysqld(_ZN6String7reallocEj+0xb1)[0x5d6471]
/usr/sbin/mysqld(_ZN6String4copyEv+0x1b)[0x5d69db]
/usr/sbin/mysqld(_Z10field_convP5FieldS0_+0x288)[0x6c3958]
/usr/sbin/mysqld(_ZN10Item_field13save_in_fieldEP5Fieldb+0x49)[0x5410c9]
/usr/sbin/mysqld(_Z12sp_eval_exprP3THDP5FieldPP4Item+0x88)[0x700b68]
/usr/sbin/mysqld(_ZN11sp_rcontext12set_variableEP3THDP5FieldPP4Item+0x1a)[0x706f6a]
/usr/sbin/mysqld(_ZN14select_dumpvar9send_dataER4ListI4ItemE+0x9f)[0x5cb80f]
/usr/sbin/mysqld[0x62d61c]
/usr/sbin/mysqld[0x63e371]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x8e5)[0x649b35]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x16e)[0x
64b52e]
/usr/sbin/mysqld(_Z13handle_selectP3THDP6st_lexP13select_resultm+0x169)[0x64be49]
/usr/sbin/mysqld[0x5e42de]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x37d7)[0x5e9bc7]
/usr/sbin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x1c)[0x6ff66c]
/usr/sbin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0xe2)[0x6ff812]
/usr/sbin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x599)[0x704a39]
/usr/sbin/mysqld(_ZN7sp_head7executeEP3THD+0x401)[0x703131]
/usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x430)[0x703860]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x106a)[0x5e745a]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x1b4)[0x5eb854]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x3d9)[0x5ec019]
/usr/sbin/mysqld(_Z10do_commandP3THD+0xc7)[0x5ed0e7]
/usr/sbin/mysqld(handle_one_connection+0x15c)[0x5e0f2c]
/lib64/libpthread.so.0[0x35fd806307]
/lib64/libc.so.6(clone+0x6d)[0x35fc4d1ded]
081024 10:50:31 - 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=67108864
read_buffer_size=262144
max_used_connections=27
max_threads=500
threads_connected=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 454317 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x2aaac4758600
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x12331790 = SELECT osLocation,binaryFile,sha1Checksum INTO osloc,bfile,md5sum FROM firmware WHERE (firmwareId= NAME_CONST('param01',7))
thd->thread_id=386982
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
na

Suggested fix:
na

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