Comment 5 for bug 1723715

Hello,

Looks that they're identical. Threat pointer is different of course, but rest of stacktrace is the same. Here's another one:

20:02:41 UTC - mysqld got signal 11 ;
[...]
key_buffer_size=67108864
read_buffer_size=131072
max_used_connections=75
max_threads=151
thread_count=40
connection_count=40
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 125262 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fab54073770
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 = 7fac2858dd40 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xed355c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7a15c1]
/lib64/libpthread.so.0(+0xf710)[0x7fac4b28d710]
/usr/sbin/mysqld(_ZN14Item_func_case7cleanupEv+0x21)[0x830711]
/usr/sbin/mysqld(_Z13cleanup_itemsP4Item+0x21)[0xca80b1]
/usr/sbin/mysqld(_ZN5TABLE16cleanup_gc_itemsEv+0x34)[0xd524d4]
/usr/sbin/mysqld(_Z19close_thread_tablesP3THD+0x5f)[0xc4eeef]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x687)[0xcaaf47]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x5d5)[0xcb2305]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xaba)[0xcb2e4a]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1b7)[0xcb4897]
/usr/sbin/mysqld(handle_connection+0x2a0)[0xd79660]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xef0464]
/lib64/libpthread.so.0(+0x79d1)[0x7fac4b2859d1]
/lib64/libc.so.6(clone+0x6d)[0x7fac4957e8fd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fab54129150): is an invalid pointer
Connection ID (thread ID): 198235
Status: NOT_KILLED

coredumps were not enabled. the are now, but have to wait for another crash.

Please find attached tgz with mysqld binary and libraries it links to.

Regards,
Konrad