debug build crashes on TRUNCATE while using innodb_fake_changes

[Valentine Gostev]

release build looks fine

http://jenkins.percona.com/view/Percona%20Server%205.1/job/percona-server-5.1-param/155/BUILD_TYPE=debug-no-Werror,Host=ubuntu-maverick-32bit/consoleText

main.percona_innodb_fake_changes w1 [ fail ]
        Test ended at 2011-09-28 19:26:29

CURRENT_TEST: main.percona_innodb_fake_changes
mysqltest: At line 44: query 'TRUNCATE TABLE t1' failed with wrong errno 2013: 'Lost connection to MySQL server during query', instead of 1180...

The result from queries just before the failure was:
< snip >
BEGIN;
INSERT INTO t1 VALUES (2);
UPDATE t1 SET a=0;
DELETE FROM t1 LIMIT 1;
SELECT * FROM t1;
a
1
COMMIT;
ERROR HY000: Got error 131 during COMMIT
SET innodb_fake_changes=default;
DROP TABLE t1;
# DDL must result in error
CREATE TABLE t1 (a INT) ENGINE=InnoDB;
SET autocommit=0;
SET innodb_fake_changes=1;
BEGIN;
CREATE TABLE t2 (a INT) ENGINE=InnoDB;
ERROR HY000: Can't create table 'test.t2' (errno: 131)
DROP TABLE t1;
ERROR 42S02: Unknown table 't1'

More results from queries before failure can be found in /home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/mysql-test/var/1/log/percona_innodb_fake_changes.log

Server [mysqld.1 - pid: 470, winpid: 470, exit: 256] failed during test run
Server log from this test:
----------SERVER LOG START-----------
mysqld: sql_class.cc:617: void Diagnostics_area::set_error_status(THD*, uint, const char*): Assertion `! is_set() || can_overwrite_status' failed.
110929 5:26:28 - 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=3
max_threads=151
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60053 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xa1754c0
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 = 0xa614936c thread_stack 0x30000
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(my_print_stacktrace+0x22) [0x85329bc]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(handle_segfault+0x28a) [0x81eae6f]
[0xb780e400]
/lib/libc.so.6(abort+0x182) [0xb7521e42]
/lib/libc.so.6(__assert_fail+0xf8) [0xb75178e8]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(Diagnostics_area::set_error_status(THD*, unsigned int, char const*)+0x3d) [0x81d583f]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(my_message_sql+0x1ce) [0x81eeb70]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(my_error+0x159) [0x851fcf4]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(ha_commit_one_phase(THD*, bool)+0xeb) [0x82fe7a1]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(ha_commit_trans(THD*, bool)+0x520) [0x82fedbc]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(end_trans(THD*, enum_mysql_completiontype)+0x11c) [0x81f9b69]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(mysql_truncate(THD*, TABLE_LIST*, bool)+0x5be) [0x8294faf]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(mysql_execute_command(THD*)+0x30af) [0x8200f6b]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x2d9) [0x8206605]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0xdf8) [0x8207c40]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(do_command(THD*)+0x2da) [0x8208e5b]
/home/jenkins/workspace/percona-server-5.1-param/BUILD_TYPE/debug-no-Werror/Host/ubuntu-maverick-32bit/Percona-Server-5.1.58-rel12.9/sql/mysqld(handle_one_connection+0x558) [0x81f70ff]
/lib/libpthread.so.0(+0x5cc9) [0xb77efcc9]
/lib/libc.so.6(clone+0x5e) [0xb75c469e]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0xa1f2db0): TRUNCATE TABLE t1
Connection ID (thread ID): 55
Status: 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-------------

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-504