Bug #28293 mysqlbinlog: corrupt SQL in hex dump mode [PATCH INCLUDED]
Submitted: 8 May 2007 2:38 Modified: 3 Jul 2007 20:46
Reporter: Jon Anderson
Status: Closed
Category:Client Severity:S3 (Non-critical)
Version:5.0.44-BK, 5.0.37 OS:Any
Assigned to: Gleb Shchepa Target Version:
Tags: Contribution

File: Maximum allowed size is 500KB.
Description:
Privacy:

If the data you need to attach is more than 500KB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (example: bug-data-28293.zip), and use FTP to upload the archive to ftp://ftp.mysql.com/pub/mysql/upload/. Once you have uploaded the file, add a comment to this bug to notify us about it. Note: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it.

All entries become the exclusive editorial property of Sun Microsystems, Inc.

[8 May 2007 2:41] Jon Anderson
Patch for sql/log_event.cc. A possible fixe for this bug.

Attachment: sql_log_event_cc.patch (application/octet-stream, text), 362 bytes.

[8 May 2007 16:05] Jon Anderson
Binary log that triggers this bug in hexdump mode.

Attachment: binlog-error (application/octet-stream, text), 349 bytes.

[8 May 2007 16:05] Jon Anderson
A binary log that does not trigger this bug.

Attachment: binlog-noerror (application/octet-stream, text), 348 bytes.