Crash due to very deep recursion in ha_innobase::wsrep_append_keys

Bug #1372288 reported by Philip Stoev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Status tracked in 5.6
5.6
Confirmed
Undecided
Unassigned

Bug Description

Running the innodb_prefix_index_restart_server test with wsrep library loaded and wsrep_cluster_address='gcomm://' causes the following:

Thread 1 (Thread 0x7f0014646700 (LWP 31815)):
#0 0x0000003f3040f128 in ?? () from /lib64/libgcc_s.so.1
#1 0x0000003f30410029 in _Unwind_Backtrace () from /lib64/libgcc_s.so.1
#2 0x0000003f2d903086 in backtrace () from /lib64/libc.so.6
#3 0x000000000091c6ec in my_print_stacktrace (stack_bottom=0x7f0014645e20 "\200\250B\003", thread_stack=262144) at /home/philips/git/codership-mysql/mysys/stacktrace.c:224
#4 0x000000000068ce67 in handle_fatal_signal (sig=11) at /home/philips/git/codership-mysql/sql/signal_handler.cc:160
#5 <signal handler called>
#6 0x00000000009df930 in ha_innobase::wsrep_append_keys (this=<optimized out>, thd=<optimized out>, shared=false, record0=0x7efff00110d8 "\376\254\r", <incomplete sequence \327>, record1=0x7efff00110c0 "\376\254\rP\250") at /home/philips/git/codership-mysql/storage/innobase/handler/ha_innodb.cc:9433
#7 0x4242424242424242 in ?? ()
#8 0x4242424242424242 in ?? ()
#9 0x4242424242424242 in ?? ()
...

The stack is 332 frames deep.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.