Older Percona server versions (like 5.5.27) are easy to crash this way with RQG:
...
121207 20:58:46 [Note] /home/openxs/dbs/p5.5/bin/mysqld: ready for connections.
Version: '5.5.27-log' socket: '/home/openxs/dbs/p5.5/mysql-test/var/tmp/master.sock' port: 19300 Source distribution
17:59:23 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=1048576
read_buffer_size=131072
max_used_connections=3
max_threads=151
thread_count=3
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60853 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x33af570
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 = 7fdf781a3e58 thread_stack 0x40000
/home/openxs/dbs/p5.5/bin/mysqld(my_print_stacktrace+0x2e)[0x7643be]
/home/openxs/dbs/p5.5/bin/mysqld(handle_fatal_signal+0x41a)[0x6592fa]
/lib64/libpthread.so.0(+0xf500)[0x7fdf7aba2500]
/home/openxs/dbs/p5.5/bin/mysqld[0x5bfc33]
/home/openxs/dbs/p5.5/bin/mysqld(_Z16explain_filenameP3THDPKcPcj26enum_explain_filename_mode+0x363)[0x5c0143]
/home/openxs/dbs/p5.5/bin/mysqld[0x7ab507]
/home/openxs/dbs/p5.5/bin/mysqld[0x7abca9]
/home/openxs/dbs/p5.5/bin/mysqld[0x806461]
/home/openxs/dbs/p5.5/bin/mysqld[0x88102e]
/home/openxs/dbs/p5.5/bin/mysqld[0x881c8b]
/home/openxs/dbs/p5.5/bin/mysqld[0x7e401e]
/home/openxs/dbs/p5.5/bin/mysqld[0x7b2b65]
/home/openxs/dbs/p5.5/bin/mysqld(_Z14ha_show_statusP3THDP10handlerton12ha_stat_type+0x333)[0x65f823]
/home/openxs/dbs/p5.5/bin/mysqld(_Z21mysql_execute_commandP3THD+0x22f7)[0x56e207]
/home/openxs/dbs/p5.5/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x33b)[0x5705ab]
/home/openxs/dbs/p5.5/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1419)[0x572199]
/home/openxs/dbs/p5.5/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x1a6)[0x601fa6]
/home/openxs/dbs/p5.5/bin/mysqld(handle_one_connection+0x4a)[0x60200a]
/lib64/libpthread.so.0(+0x7851)[0x7fdf7ab9a851]
/lib64/libc.so.6(clone+0x6d)[0x7fdf79b0511d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fdf540048e0): SHOW ENGINE INNODB STATUS
Connection ID (thread ID): 5
...
Oracle's 5.6.8-rc passed without crashes in the same environment.
Older Percona server versions (like 5.5.27) are easy to crash this way with RQG:
... dbs/p5. 5/bin/mysqld: ready for connections. openxs/ dbs/p5. 5/mysql- test/var/ tmp/master. sock' port: 19300 Source distribution bugs.percona. com/
121207 20:58:46 [Note] /home/openxs/
Version: '5.5.27-log' socket: '/home/
17:59:23 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://
key_buffer_ size=1048576 size=131072 connections= 3 size)*max_ threads = 60853 K bytes of memory
read_buffer_
max_used_
max_threads=151
thread_count=3
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x33af570 dbs/p5. 5/bin/mysqld( my_print_ stacktrace+ 0x2e)[0x7643be] dbs/p5. 5/bin/mysqld( handle_ fatal_signal+ 0x41a)[ 0x6592fa] libpthread. so.0(+0xf500) [0x7fdf7aba2500 ] dbs/p5. 5/bin/mysqld[ 0x5bfc33] dbs/p5. 5/bin/mysqld( _Z16explain_ filenameP3THDPK cPcj26enum_ explain_ filename_ mode+0x363) [0x5c0143] dbs/p5. 5/bin/mysqld[ 0x7ab507] dbs/p5. 5/bin/mysqld[ 0x7abca9] dbs/p5. 5/bin/mysqld[ 0x806461] dbs/p5. 5/bin/mysqld[ 0x88102e] dbs/p5. 5/bin/mysqld[ 0x881c8b] dbs/p5. 5/bin/mysqld[ 0x7e401e] dbs/p5. 5/bin/mysqld[ 0x7b2b65] dbs/p5. 5/bin/mysqld( _Z14ha_ show_statusP3TH DP10handlerton1 2ha_stat_ type+0x333) [0x65f823] dbs/p5. 5/bin/mysqld( _Z21mysql_ execute_ commandP3THD+ 0x22f7) [0x56e207] dbs/p5. 5/bin/mysqld( _Z11mysql_ parseP3THDPcjP1 2Parser_ state+0x33b) [0x5705ab] dbs/p5. 5/bin/mysqld( _Z16dispatch_ command19enum_ server_ commandP3THDPcj +0x1419) [0x572199] dbs/p5. 5/bin/mysqld( _Z24do_ handle_ one_connectionP 3THD+0x1a6) [0x601fa6] dbs/p5. 5/bin/mysqld( handle_ one_connection+ 0x4a)[0x60200a] libpthread. so.0(+0x7851) [0x7fdf7ab9a851 ] libc.so. 6(clone+ 0x6d)[0x7fdf79b 0511d]
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 = 7fdf781a3e58 thread_stack 0x40000
/home/openxs/
/home/openxs/
/lib64/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fdf540048e0): SHOW ENGINE INNODB STATUS
Connection ID (thread ID): 5
...
Oracle's 5.6.8-rc passed without crashes in the same environment.