Description:
Master based on mysql-5.1-wl2325-5.0-drop6 clone crashed during execution rpl_user_variables test case (from rpl suite). master.err log likes that:
071015 14:16:12 InnoDB: Started; log sequence number 0 43655
071015 14:16:12 [Note] ../../5.1-alcatel//libexec/mysqld: ready for connections.
Version: '5.2.1-a_drop6p10-log' socket: '/data2/skozlov/builds/5.1-new-rpl/mysq
l-test/var/tmp/master.sock' port: 9306 Source distribution
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=1048576
read_buffer_size=131072
max_used_connections=4
max_connections=100
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 39423
K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x9dffb78
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...
Cannot determine thread, fp=0x64cea8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81a9473
0x2cd420
(nil)
0x82df9d1
0x82df744
0x81f5ef5
0x81c4325
0x81cc550
0x81ccbbd
0x81ce90e
0x45ebd4
0x3b64fe
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow
instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x9e0b098 = insert into t1 select * FROM (select @var1 union sele
ct @var2) AS t2
thd->thread_id=2
How to repeat:
1. Install mysql mysql-5.1-wl2325-5.0-drop6
2. Install mysql 5.1.22
3. Copy m4r.pl (patched mtr) into 5.1.22/mysql-test
4. Run test case:
./m4r.pl --master-basedir=/path/to/mysql-5.1-wl2325-5.0-drop6 --suite=rpl
--mysqld=--binlog-format=row rpl_user_variables
5. Look at master.err