MySQL Bugs: #55935: crash when printing deadlock information...

Bug #55935	crash when printing deadlock information...
Submitted:	12 Aug 2010 7:24	Modified:	30 Apr 2012 11:53
Reporter:	Shane Bester (Platinum Quality Contributor)	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	5.0.72,5.1.49, 5.1.56	OS:	Windows
Assigned to:		CPU Architecture:	Any

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

some infos

Attachment: bug55935_5.1.49_crash_info.txt (text/plain), 17.17 KiB.

some infos.

Attachment: 5.0.72_some_crash_infos.txt (text/plain), 13.83 KiB.

note tos elf: 15 threads, shuffled for about 30 minutes is enough to see a crash on 5.1 builtin.

Attachment: dml.sql (, text), 1.27 KiB.