Comment 5 for bug 1670332

Revision history for this message
Jericho Rivera (jericho-rivera) wrote : Re: percona server 5.7 crashes with signal 11 Item_func4walkE in backtrace

Reproducible on 5.7.17 as well.

12:07:43 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

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

Thread pointer: 0x7f71b400e5f0
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 = 7f720852ce40 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xecec9c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x79f531]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f726b530330]
/usr/sbin/mysqld(_ZN9Item_func4walkEM4ItemFbPhENS0_9enum_walkES1_+0x83)[0x863b53]
/usr/sbin/mysqld(_ZN9Item_func4walkEM4ItemFbPhENS0_9enum_walkES1_+0x89)[0x863b59]
/usr/sbin/mysqld[0xd47108]
/usr/sbin/mysqld(_ZN5TABLE14refix_gc_itemsEP3THD+0xe4)[0xd4f8d4]
/usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0x388)[0xc4e6f8]
/usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x5f2)[0xc55f02]
/usr/sbin/mysqld(_Z21open_tables_for_queryP3THDP10TABLE_LISTj+0x4b)[0xc5681b]
/usr/sbin/mysqld[0xd09e6d]
/usr/sbin/mysqld(_Z14get_all_tablesP3THDP10TABLE_LISTP4Item+0x6e2)[0xd0a762]
/usr/sbin/mysqld[0xcf37cc]
/usr/sbin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x1e1)[0xd06591]
/usr/sbin/mysqld(_ZN4JOIN14prepare_resultEv+0x6d)[0xce960d]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x80)[0xc79cb0]
/usr/sbin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x17d)[0xce9f3d]
/usr/sbin/mysqld[0x75f5a3]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x4551)[0xcacc91]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x5c5)[0xcb0185]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xaba)[0xcb0cca]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1b7)[0xcb2647]
/usr/sbin/mysqld(handle_connection+0x2a0)[0xd76ad0]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0x124c234]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7f726b528184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f726aa3537d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f71b40175f0): SHOW TABLE STATUS FROM `testdb` LIKE 'testtbl'
Connection ID (thread ID): 37
Status: NOT_KILLED

I had to slightly modify the python script
#await cur.execute("SELECT GUID from testtbl where ID={0};".format(random.randint(16658, 821445)))
await cur.execute("SHOW TABLE STATUS FROM `testdb` LIKE 'testtbl'")