Comment 8 for bug 1295672

Revision history for this message
monty solomon (monty+launchpad) wrote :

old
5.5.35-33.0-log Percona Server (GPL), Release rel33.0, Revision 611

new
5.6.16-64.2-56-log Percona Server (GPL), Release 64.2, Revision 569

21:48:19 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
key_buffer_size=67108864
read_buffer_size=1048576
max_used_connections=0
max_threads=502
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1614987 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8ca6d5]
/usr/sbin/mysqld(handle_fatal_signal+0x4c4)[0x645024]
/lib64/libpthread.so.0(+0xf710)[0x7f642fa76710]
/usr/sbin/mysqld[0xa73127]
/usr/sbin/mysqld[0xa77df9]
/usr/sbin/mysqld[0x9edf0f]
/usr/sbin/mysqld[0x92aee4]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x588a28]
/usr/sbin/mysqld[0x6d45b1]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xb5e)[0x6d818e]
/usr/sbin/mysqld[0x57b5b4]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x455)[0x580635]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7f642e0c3d1d]
/usr/sbin/mysqld[0x571b31]