Bug #51019 crash/invalid memory accesses after an error occurs with binlogging
Submitted: 9 Feb 2010 9:25 Modified: 30 Mar 2010 8:50
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Replication Severity:S1 (Critical)
Version:5.1.43, 5.1.45-bzr OS:Any
Assigned to: Assigned Account CPU Architecture:Any
Tags: assertion, crash, valgrind

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:

[9 Feb 2010 9:27] Shane Bester
uncut valgrind output from 5.1.43

Attachment: bug51019_full_valgrind_output_5.1.43.txt (text/plain), 70.08 KiB.