mysqlbinlog --verbose (-v) Crashes When Reading Corrupt Binlog, or Active Binlog Being Updated By Server

(Doc ID 1610628.1)

Last updated on FEBRUARY 20, 2016

Applies to:

MySQL Server - Version 5.5 and later
Information in this document applies to any platform.


Reading incomplete, truncated, or corrupted binlogs with mysqlbinlog -v can cause it to crash with similar stack trace:

mysqlbinlog.exe!my_b_write_quoted  Line 1506
mysqlbinlog.exe!log_event_print_value Line 1849
mysqlbinlog.exe!Rows_log_event::print_verbose_one_row  Line 1928
mysqlbinlog.exe!Rows_log_event::print_verbose Line 2008
mysqlbinlog.exe!Log_event::print_base64  Line 2096
mysqlbinlog.exe!Rows_log_event::print_helper Line 8111
mysqlbinlog.exe!process_event Line 990
mysqlbinlog.exe!dump_local_log_entries  Line 2011
mysqlbinlog.exe!dump_log_entries  Line 1460
mysqlbinlog.exe!main  Line 2107


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms