| Bug #1340 | mysqlbinlog coredumps when reading possibly broken binlog | ||
|---|---|---|---|
| Submitted: | 18 Sep 2003 14:36 | Modified: | 19 Sep 2003 11:43 |
| Reporter: | Dmitri Lenev | ||
| Status: | Closed | ||
| Category: | Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 4.0.15 | OS: | Linux (Linux) |
| Assigned to: | Dmitri Lenev | Target Version: | |
[18 Sep 2003 14:36]
Dmitri Lenev
[18 Sep 2003 14:38]
Dmitri Lenev
I was able to repeat this with 4.0 version from bk and customer binlog.
[19 Sep 2003 7:49]
Dmitri Lenev
Actually the binlog provided is ok. The problem is in mysqlbinlog which coredumps if mets Exec_load_log_event without corresponding Create_file_log_event (which is normal situation if Create_file event is in other binlog file).
[19 Sep 2003 11:43]
Dmitri Lenev
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 bugfix, yourself. More information
about accessing the source trees is available at
http://www.mysql.com/doc/en/Installing_source_tree.html
ChangeSet 1.1578 2003/09/19 20:31:01 dlenev@mysql.com
Bugfix for bug #1340
