Comment 0 for bug 1053342

The latest 5.5.27-28.1 Percona Server crashes when the following list of things happens:

- execute a update statement using a variable
- slave server has replicate-wild-ignore-table or replicate-ignore-table on my.cnf

MASTER: 5.5.24-rel26.0-log

(default sandbox my.cnf)

[mysql]
prompt='mysql [\h] {\u} (\d) > '
#

[client]
user = msandbox
password = msandbox
port = 5524
socket = /tmp/mysql_sandbox5524.sock

[mysqld]
user = root
port = 5524
socket = /tmp/mysql_sandbox5524.sock
basedir = /root/5.5.24
datadir = /root/sandboxes/msb_5_5_24/data
tmpdir = /root/sandboxes/msb_5_5_24/tmp
pid-file = /root/sandboxes/msb_5_5_24/data/mysql_sandbox5524.pid
#log-slow-queries = /root/sandboxes/msb_5_5_24/data/msandbox-slow.log
#log = /root/sandboxes/msb_5_5_24/data/msandbox.log
#
# additional options passed through 'my_clause'
#
log-error=msandbox.err
server_id=1
log-bin=a

SLAVE: 5.5.27-28.1 Percona Server

root@debian:/var/lib/mysql# cat /etc/my.cnf
[mysqld]
datadir=/var/lib/mysql
innodb_file_per_table=1
innodb_file_format=barracuda
server_id=2
replicate-wild-ignore-table=test.%
replicate-ignore-table=mysql.user

master> create table t (i int, a char(10), b char(11));
master> update t set i=@var+1 where i=@var;

slave> show slave status\G
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR:
Can't connect to the server

1:04:07 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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338618 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2b04580
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 = 7f9e92a59ea8 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7c6395]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6967e4]
/lib/libpthread.so.0(+0xeff0)[0x7f9ea2a33ff0]
/lib/libc.so.6(+0x10dd3a)[0x7f9ea1d0ad3a]
/usr/sbin/mysqld(_ZN5TABLE4initEP3THDP10TABLE_LIST+0x4c)[0x6111cc]
/usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0x148)[0x55eba8]
/usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x4f6)[0x560436]
/usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0xa9)[0x6087a9]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x13e4)[0x5970d4]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x333)[0x59a853]
/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0xd04)[0x745144]
/usr/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x125)[0x533815]
/usr/sbin/mysqld[0x538359]
/usr/sbin/mysqld(handle_slave_sql+0x949)[0x539799]
/lib/libpthread.so.0(+0x68ca)[0x7f9ea2a2b8ca]
/lib/libc.so.6(clone+0x6d)[0x7f9ea1ccc92d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2b436a0): ?6?
Connection ID (thread ID): 1
Status: NOT_KILLED

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.