Bug #40437 mysqld segfault on my_hash_insert and XA
Submitted: 30 Oct 2008 16:06 Modified: 30 Oct 2008 17:31
Reporter: Adam Erickson Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:5.1.28 OS:Linux (CentOS release 5 (Final))
Assigned to: CPU Architecture:Any
Tags: mysqld segfault crash XA

[30 Oct 2008 16:06] Adam Erickson
Error log:
081030 11:55:00 - 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.

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

thd: 0x2aab640eee60
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...
stack_bottom = 0x45458110 thread_stack 0x40000
/opt/mysql/bin/mysqld(my_print_stacktrace+0x20) [0x9f64f8]
/opt/mysql/bin/mysqld(handle_segfault+0x368) [0x5f983a]
/lib64/libpthread.so.0 [0x3f4800de70]
/opt/mysql/bin/mysqld(my_hash_insert+0x5d4) [0x9e526e]
/opt/mysql/bin/mysqld(xid_cache_insert(st_xid_state*)+0x1c) [0x5e1948]
/opt/mysql/bin/mysqld(mysql_execute_command(THD*)+0xa7d) [0x605b29]
/opt/mysql/bin/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x20a) [0x60
/opt/mysql/bin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x1344
) [0x60455c]
/opt/mysql/bin/mysqld(do_command(THD*)+0x114) [0x603214]
/opt/mysql/bin/mysqld(handle_one_connection+0xd31) [0x5fe60d]
/lib64/libpthread.so.0 [0x3f480062f7]
/lib64/libc.so.6(clone+0x6d) [0x3f478ce85d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x254895a0 = XA START 0x312d2d35336566663437353a616563313a34393037386538623a323
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.
081030 11:55:01 mysqld_safe Number of processes running now: 0
081030 11:55:01 mysqld_safe mysqld restarted
InnoDB: Log scan progressed past the checkpoint lsn 70 1950904032
081030 11:55:02  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.

How to repeat:

Suggested fix:
Not crash.
[30 Oct 2008 16:10] MySQL Verification Team
this is a duplicate of bug #28323 (currently marked as private)
[30 Oct 2008 17:31] Adam Erickson
bug #28323 is marked as private, is there any information on this bug I could use to avoid this issue until a patch is released?

Would downgrading to 5.1.26 solve it temporarily?