Description:
flush_read_lock hits an assertion after mysql-trunk was merged
with mysql-trunk-bugfixing. In this merge, only WL#2540 was brought
from mysql-trunk into mysql-trunk-bugfixing.
The failure exhibits the following symptom:
main.flush_read_lock w10 [ fail ]
Test ended at 2010-11-29 13:39:12
CURRENT_TEST: main.flush_read_lock
mysqltest: At line 322: query 'BINLOG '
MfmqTA8BAAAAZwAAAGsAAAABAAQANS41LjctbTMtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAx+apMEzgNAAgAEgAEBAQEEgAAVAAEGggAAAAICAgCAA==
'' failed: 2013: Lost connection to MySQL server during query
The result from queries just before the failure was:
< snip >
set debug_sync='now WAIT_FOR parked';
flush tables with read lock;
# Switching to connection 'con2'. # Wait until FTWRL is blocked.
set debug_sync='now SIGNAL go';
# Switching to connection 'default'. # Reap COMMIT. # Switching to connection 'con1'. # Reap FTWRL.
unlock tables;
# Switching to connection 'default'.
delete from t3_trans;
set debug_sync= "RESET";
# We don't run similar test for BEGIN and ROLLBACK as # they release metadata locks in non-standard place. # # 4) BINLOG statement should be incompatible with FTWRL. # # # Provide format description BINLOG statement first.
More results from queries before failure can be found in /tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/mysql-test/var-main-ps_row/10/log/flush_read_lock.log
Server [mysqld.1 - pid: 25799, winpid: 25799, exit: 256] failed during test run
Server log from this test:
----------SERVER LOG START-----------
Assertion failed: ret == BINLOG_CHECKSUM_ALG_OFF || ret == BINLOG_CHECKSUM_ALG_UNDEF || ret == BINLOG_CHECKSUM_ALG_CRC32, file /tmp/pb2/build/sb_1-2604478-1291032165.37/mysql-5.6.1-m5/sql/log_event.cc, line 4611
101129 15:39:07 - mysqld got signal 6 ;
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_threads=151
thread_count=4
connection_count=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60815 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x103d93f60
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...
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:my_print_stacktrace+0x38
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:handle_segfault+0x45c
/lib/sparcv9/libc.so.1:0xd418c
/lib/sparcv9/libc.so.1:0xc7d28
/lib/sparcv9/libc.so.1:0xc7f20
/lib/sparcv9/libc.so.1:_lwp_kill+0x8 [ Signal 6 (ABRT)]
/lib/sparcv9/libc.so.1:abort+0xd0
/lib/sparcv9/libc.so.1:_assert+0x74
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:__1cQget_checksum_alg6FpkcL_C_+0x18c
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:__1cJLog_eventOread_log_event6FpkcIp2pknbCFormat_description_log_event_c_p0_+0x20c
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:__1cbDmysql_client_binlog_statement6FpnDTHD__v_+0x59c
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:__1cVmysql_execute_command6FpnDTHD__i_+0x8660
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:__1cLmysql_parse6FpnDTHD_pcIpnMParser_state__v_+0x31c
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:__1cQdispatch_command6FnTenum_server_command_pnDTHD_pcI_b_+0x834
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:__1cKdo_command6FpnDTHD__b_+0x354
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:__1cYdo_handle_one_connection6FpnDTHD__v_+0x338
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:handle_one_connection+0x2c
/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/bin/mysqld:pfs_spawn_thread+0x158
/lib/sparcv9/libc.so.1:0xd4060
Please read http://dev.mysql.com/doc/refman/5.1/en/resolve-stack-dump.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 103dafe60 = BINLOG '
MfmqTA8BAAAAZwAAAGsAAAABAAQANS41LjctbTMtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAx+apMEzgNAAgAEgAEBAQEEgAAVAAEGggAAAAICAgCAA==
'
thd->thread_id=9
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file
----------SERVER LOG END-------------
- saving '/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/mysql-test/var-main-ps_row/10/log/main.flush_read_lock/' to '/tmp/pb2/test/sb_0-2604685-1291032784.86/mysql-5.6.1-m5-solaris10-sparc-64bit-test/mysql-test/var-main-ps_row/log/main.flush_read_lock/'
- found 'core' (0/5)
Trying 'dbx' to get a backtrace
sh: dbx: not found
Trying 'gdb' to get a backtrace
How to repeat:
clone mysql-trunk-bugfixing, build with debug info and run
main.flush_read_lock test case.
Suggested fix:
.
