Bug #31793 log event corruption causes crash
Submitted: 23 Oct 2007 17:26 Modified: 28 Nov 2007 12:40
Reporter: Matthew Lord Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Replication Severity:S1 (Critical)
Version:5.0.46,5.1.23bk OS:Any (64 bit)
Assigned to: Mats Kindahl CPU Architecture:Any
Tags: bfsm_2007_10_25, binary log, corruption, crash, relay log, replication

[23 Oct 2007 17:26] Matthew Lord
You can see the routines not handle the corruption well and crash on any x86_64
machine with greater than 4GB of RAM using the attached relay log:
mysqlbinlog relay-bin.000624 > /tmp/relay.out

How to repeat:
grab attached relay log file and run the following command on an x86_64 machine
with > 4GB of RAM:

mysqlbinlog relay-bin.000624 > /tmp/relay.out

Suggested fix:
We should handle this situation more gracefully.  Anytime we crash it is dangerous for myisam tables.
[23 Oct 2007 17:39] Shane Bester
stack trace, debug info, etc.   mysqld crashes in same place (according to customer).

Attachment: bug31793_stack_debug.txt (text/plain), 3.04 KiB.

[12 Nov 2007 21:02] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:


ChangeSet@1.2551, 2007-11-12 22:02:12+01:00, mats@kindahl-laptop.dnsalias.net +1 -0
  BUG#31793 (log event corruption causes crash):
  Corrections to get_str_len_and_pointer().
[27 Nov 2007 10:49] Bugs System
Pushed into 5.0.54
[27 Nov 2007 10:50] Bugs System
Pushed into 5.1.23-rc
[27 Nov 2007 10:52] Bugs System
Pushed into 6.0.4-alpha
[28 Nov 2007 12:40] Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at


Documented bugfix in 5.0.54, 5.1.23, and 6.0.4 changelogs as follows:

        Corruption of log events caused the server to crash on 64-bit
        Linux systems having 4 GB of memory or more.