rpl.rpl_row_index_choice failed in buildbot, slave server crashed

rpl.rpl_row_index_choice 'innodb_plugin,row' w1 [ fail ]

        Test ended at 2018-01-11 11:54:10

CURRENT_TEST: rpl.rpl_row_index_choice

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

Server log from this test:

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

180111 11:54:06 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16000', master_log_file='', master_log_pos='4'. New state master_host='127.0.0.1', master_port='16000', master_log_file='master-bin.000001', master_log_pos='4'.

180111 11:54:06 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication started in log 'master-bin.000001' at position 4

180111 11:54:06 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 4, relay log './slave-relay-bin.000001' position: 4

180111 11:54:08 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/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: 5.5.59-MariaDB-debug

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=5

max_threads=153

thread_count=4

It is possible that mysqld could use up to 

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

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

Thread pointer: 0x0

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 = 0x0 thread_stack 0x48000

mysys/stacktrace.c:246(my_print_stacktrace)[0x88de614]

sql/signal_handler.cc:155(handle_fatal_signal)[0x83da313]

[0xb76e8400]

dbug/dbug.c:2141(_db_flush_)[0x88f8bd1]

perfschema/pfs.cc:1101(get_thread_mutex_locker_v1)[0x8566c3f]

/mnt/buildbot/build/mariadb-5.5.59/mysql-test/var/1/plugins/ha_innodb.so(+0x49934)[0xb463f934]

/mnt/buildbot/build/mariadb-5.5.59/mysql-test/var/1/plugins/ha_innodb.so(+0x4eba8)[0xb4644ba8]

/mnt/buildbot/build/mariadb-5.5.59/mysql-test/var/1/plugins/ha_innodb.so(+0x4edc7)[0xb4644dc7]

/mnt/buildbot/build/mariadb-5.5.59/mysql-test/var/1/plugins/ha_innodb.so(+0x4f3e0)[0xb46453e0]

/mnt/buildbot/build/mariadb-5.5.59/mysql-test/var/1/plugins/ha_innodb.so(+0x18f253)[0xb4785253]

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

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

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

mysqltest failed but provided no output

The result from queries just before the failure was:

< snip >

DROP TABLE t2;

CREATE TABLE t2 (a INT NOT NULL, b INT NOT NULL, c INT NOT NULL, d INT NOT NULL,

KEY expected_key(b),

KEY wrong_key7(d),

KEY wrong_key8(c)) ENGINE=myisam;

INSERT INTO t2 SELECT d DIV 10, d MOD 41, d MOD 37, d FROM t1;

# Slave will crash if using the wrong or no index

SET GLOBAL debug_dbug="+d,slave_crash_if_wrong_index,slave_crash_if_table_scan";

UPDATE t2 SET d=10042 WHERE d=42;

DELETE FROM t2 WHERE d=53;

SET GLOBAL debug_dbug="";

SELECT * FROM t2 WHERE d IN (10042,53);

a	b	c	d

4	1	5	10042

DROP TABLE t2;

CREATE TABLE t2 (a INT NOT NULL, b INT NOT NULL, c INT NOT NULL, d INT,

UNIQUE wrong_key9(d),

KEY wrong_key10(a),

PRIMARY KEY expected_key(c,b)) ENGINE=innodb;

INSERT INTO t2 SELECT d DIV 10, d MOD 41, d MOD 37, d FROM t1;