Bug #57173 crash with repair table and delay key writes
Submitted: 1 Oct 2010 13:56 Modified: 30 Dec 2014 19:19
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: MyISAM storage engine Severity:S1 (Critical)
Version:5.1.51 OS:Any (FC13 x64)
Assigned to: CPU Architecture:Any
Tags: repair table, valgrind

[1 Oct 2010 13:56] Shane Bester 
Description:
when testing bug #57168 with --delay-key-write=all i ran repair table in another thread and it crashed:

Invalid read of size 1
at: do_lookup_x (dl-lookup.c:110)
by: _dl_lookup_symbol_x (dl-lookup.c:736)
by: _dl_fixup (dl-runtime.c:118)
by: _dl_runtime_resolve (dl-trampoline.S:41)
by: my_chsize (my_chsize.c:70)
by: mi_repair_by_sort (mi_check.c:2520)
by: ha_myisam::repair (ha_myisam.cc:1148)
by: ha_myisam::repair (ha_myisam.cc:1031)
by: handler::ha_repair (handler.cc:3158)
by: mysql_admin_table (sql_table.cc:4810)
by: mysql_repair_table (sql_table.cc:5071)
by: mysql_execute_command (sql_parse.cc:3049)
Address 0x6e055dd786bb0319 is not stack'd, malloc'd or (recently) free'd

How to repeat:
simmilar to bug #57168 but much harder! only happened once.
[1 Oct 2010 14:52] Valeriy Kravchuk 
Should I run

show table status like 't2';

in the second thread as in that other bug, or something else? (repair table t2?)
[2 Nov 2010 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[30 Dec 2014 19:19] MySQL Verification Team 
Cannot repeat on 5.6.  I believe the invention of MDL probably had a good effect here.