[#MDEV-11662] Crashdumps are not used in buildbot even if created

Sometimes mysqld crashes leaving a dmp file, which can be used to output stack traces, local variables etc on buildbot
However mtr is not using it . It used to do so in the past, and would cdb debugger (which is installed on the machines) which would produce a lot of helpful for troubleshooting information

CURRENT_TEST: main.bootstrap

mysqltest: At line 45: command "$MYSQLD_BOOTSTRAP_CMD < $MYSQLTEST_VARDIR/tmp/long_query.sql >> $MYSQLTEST_VARDIR/tmp/bootstrap.log 2>&1" failed with wrong error: 255

The result from queries just before the failure was:

drop table if exists t1;

drop table t1;

drop table t1;

ERROR 42S02: Unknown table 'test.t1'

set @my_max_allowed_packet= @@max_allowed_packet;

set global max_allowed_packet=100*@@max_allowed_packet;

 - saving 'D:/win32-debug/build/mysql-test/var/3/log/main.bootstrap/' to 'D:/win32-debug/build/mysql-test/var/log/main.bootstrap/'

 - found 'mysqld.dmp' (0/5)

buildbot.mariadb.org (MDEV-8244) [MDEV-11662] Crashdumps are not used in buildbot even if created Created: 2016-12-23 Updated: 2017-05-26
Status:	Open
Project:	MariaDB Server
Component/s:	Tests
Affects Version/s:	None
Fix Version/s:	None

[MDEV-11662] Crashdumps are not used in buildbot even if created Created: 2016-12-23 Updated: 2017-05-26