MySQL Bugs: #38715: slave crashed with concurrent kill/stop/start/reset

Bug #38715	slave crashed with concurrent kill/stop/start/reset
Submitted:	11 Aug 2008 10:56	Modified:	1 Sep 2009 8:20
Reporter:	Shane Bester (Platinum Quality Contributor)	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	5.0.66a, 5.1.26	OS:	Any
Assigned to:	Andrei Elkin	CPU Architecture:	Any
Tags:	crash, KILL, RESET SLAVE, start slave, stop slave

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

full stack trace and variables in frame. 5.0.66a

Attachment: bug38715_some_info.txt (text/plain), 3.07 KiB.

testcase that will expose a few different assertions if run as described above.

Attachment: bug38715.c (text/plain), 6.49 KiB.