Bug #89452 command "show status" cause mysqld crash,mysqld got signal 11
Submitted: 29 Jan 2018 9:55 Modified: 12 Jul 2019 10:15
Reporter: Demon Chen Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:5.6.23 OS:CentOS
Assigned to: CPU Architecture:Any
Tags: crash, siganl 11, slave

[29 Jan 2018 9:55] Demon Chen
Description:
MySQL got signal 11 (detailed error log attached below).All this situation occured at slave instance.when executed the show status command, mysqld crashed and restart automatically. 

08:36:40 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.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1011
max_threads=3100
thread_count=8
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 19121575 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x47526870
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 = 7fa8e2a2de28 thread_stack 0x30000
/export/servers/app/mysql-5.6.23/bin/mysqld(my_print_stacktrace+0x35)[0x8e6145]
/export/servers/app/mysql-5.6.23/bin/mysqld(handle_fatal_signal+0x41b)[0x652c4b]
/lib64/libpthread.so.0(+0xf710)[0x7fb411025710]
/lib64/libc.so.6(memcpy+0xd2)[0x7fb40fd27a22]
/export/servers/app/mysql-5.6.23/bin/mysqld(_ZN6String6appendEPKcj+0xde)[0x71f04e]
/export/servers/app/mysql-5.6.23/bin/mysqld(thd_security_context+0x17c)[0x6a193c]
/export/servers/app/mysql-5.6.23/bin/mysqld[0x9355d5]
/export/servers/app/mysql-5.6.23/bin/mysqld[0x963f07]
/export/servers/app/mysql-5.6.23/bin/mysqld[0x9e3a64]
/export/servers/app/mysql-5.6.23/bin/mysqld[0x941b76]
/export/servers/app/mysql-5.6.23/bin/mysqld(_Z14ha_show_statusP3THDP10handlerton12ha_stat_type+0x3ce)[0x59518e]
/export/servers/app/mysql-5.6.23/bin/mysqld(_Z21mysql_execute_commandP3THD+0x2aad)[0x6daa3d]
/export/servers/app/mysql-5.6.23/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x4c7)[0x6dcf47]
/export/servers/app/mysql-5.6.23/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x189c)[0x6de8fc]
/export/servers/app/mysql-5.6.23/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x10d)[0x6a655d]
/export/servers/app/mysql-5.6.23/bin/mysqld(handle_one_connection+0x42)[0x6a6692]
/export/servers/app/mysql-5.6.23/bin/mysqld(pfs_spawn_thread+0x127)[0x921057]
/lib64/libpthread.so.0(+0x79d1)[0x7fb41101d9d1]
/lib64/libc.so.6(clone+0x6d)[0x7fb40fd86b6d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fa608014e30): is an invalid pointer
Connection ID (thread ID): 15022943
Status: 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.
180129 16:36:40 mysqld_safe Number of processes running now: 0
180129 16:36:40 mysqld_safe mysqld restarted

How to repeat:
unknown how to repeat
[29 Jan 2018 10:32] MySQL Verification Team
Thank you for taking the time to report a problem.  Unfortunately you
are not using a current version of the product you reported a problem
with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/.

Also, there is no test case provided in the bug report and hence there
is nothing we can verify here.  If you are able to reproduce the bug
with one of the latest versions, please attach the exact reproducible
test case and change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for your
continued support of MySQL.