gcol.innodb_virtual_debug 'innodb'       w2 [ fail ]

        Test ended at 2017-10-24 22:18:29

CURRENT_TEST: gcol.innodb_virtual_debug

mysqltest: At line 87: query 'DELETE FROM t WHERE a = 0' failed: 2013: Lost connection to MySQL server during query

The result from queries just before the failure was:

< snip >

start transaction;

update t set b=b+1;

rollback;

SET DEBUG_SYNC = 'now SIGNAL go_ahead';

connection default;

check table t;

Table	Op	Msg_type	Msg_text

test.t	check	status	OK

SELECT c FROM t;

c

NULL

3

19

29

SET DEBUG_SYNC = 'innodb_inplace_alter_table_enter SIGNAL start_create WAIT_FOR go_ahead';

ALTER TABLE t ADD COLUMN x2 INT;

connection con1;

SET DEBUG_SYNC = 'now WAIT_FOR start_create';

start transaction;

DELETE FROM t WHERE a = 0;

More results from queries before failure can be found in /mnt/buildbot/build/mariadb-10.3.3/mysql-test/var/2/log/innodb_virtual_debug.log

Server [mysqld.1 - pid: 22229, winpid: 22229, exit: 256] failed during test run

Server log from this test:

----------SERVER LOG START-----------

2017-10-24 22:18:28 44 [ERROR] InnoDB: Record in index `idx` of table `test`.`t` was not found on update: TUPLE (info_bits=0, 2 fields): {[4]    (0x00000000),[6]     b(0x000000000802)} at: COMPACT RECORD(info_bits=0, 2 fields): {NULL,[6]     e(0x000000000805)}

2017-10-24 22:18:28 44 [Note] InnoDB: GIS MBR INFO: 6.32404e-322 and 3.23508e-316, -nan, -2.18566e-311

mysqld: /home/buildbot/buildbot/build/mariadb-10.3.3/storage/innobase/row/row0upd.cc:2427: dberr_t row_upd_sec_index_entry(upd_node_t*, que_thr_t*): Assertion `0' failed.

171024 22:18:28 [ERROR] 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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.3.3-MariaDB-debug-log

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=2

max_threads=153

thread_count=8

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61908 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xabb08108

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 = 0xacab82a0 thread_stack 0x49000

/mnt/buildbot/build/mariadb-10.3.3/sql/mysqld(my_print_stacktrace+0x3b)[0x8df3153]

/mnt/buildbot/build/mariadb-10.3.3/sql/mysqld(handle_fatal_signal+0x3cf)[0x863fb53]

[0xb776b400]

[0xb776b424]

/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f)[0xb72471ef]

/lib/i386-linux-gnu/libc.so.6(abort+0x175)[0xb724a835]

/lib/i386-linux-gnu/libc.so.6(+0x27095)[0xb7240095]

/lib/i386-linux-gnu/libc.so.6(+0x27147)[0xb7240147]

/mnt/buildbot/build/mariadb-10.3.3/sql/mysqld[0x8b1bf85]

/mnt/buildbot/build/mariadb-10.3.3/sql/mysqld[0x8b1c6c1]

/mnt/buildbot/build/mariadb-10.3.3/sql/mysqld[0x8b1edd5]

mysys/stacktrace.c:269(my_print_stacktrace)[0x8b1f122]

row/row0upd.cc:2431(row_upd_sec_index_entry)[0x8aba8fc]

handler/ha_innodb.cc:9245(ha_innobase::delete_row(unsigned char const*))[0x8966932]

sql/handler.cc:6110(handler::ha_delete_row(unsigned char const*))[0x864fea7]

sql/sql_delete.cc:637(mysql_delete(THD*, TABLE_LIST*, Item*, SQL_I_List<st_order>*, unsigned long long, unsigned long long, select_result*))[0x87dd5c7]

sql/sql_parse.cc:4883(mysql_execute_command(THD*))[0x838f83a]

sql/sql_parse.cc:7921(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x8399aa3]

sql/sql_parse.cc:1821(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x83867ed]

sql/sql_parse.cc:1370(do_command(THD*))[0x83852a7]

sql/sql_connect.cc:1418(do_handle_one_connection(CONNECT*))[0x84cdb17]

sql/sql_connect.cc:1325(handle_one_connection)[0x84cd8a5]

perfschema/pfs.cc:1864(pfs_spawn_thread)[0x8862625]

/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb74f3d4c]

/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb7303ace]

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0xabb17d38): DELETE FROM t WHERE a = 0

Connection ID (thread ID): 44

Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_grouping_derived=on

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-------------