Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.11, 12.3
-
None
Description
$ hexdump -X loop.001
|
0000000 fe 62 69 6e 01 02 03 04 03 01 00 00 00 00 0d 00
|
0000010 00
|
0000011
|
$ mariadb-binlog --force-read loop.001
|
/*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;
|
/*!40019 SET @@session.max_delayed_threads=0*/;
|
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
|
DELIMITER /*!*/;
|
# at 4
|
# Encrypted event
|
# at 4
|
# Encrypted event
|
# at 4
|
# Encrypted event
|
[continuously repeats...]
|
To be fair, such an occurrence makes a corrupt binlog file (truncated or has trailing garbage), so what mariadb-binlog spits out could be anyone's guess.
But infinite loops in general are definitely unexpected.
Not to mention that such a short "event" is at most a "compressed" event, not an 'Encrypted' event.
Attachments
Issue Links
- split from
-
MDEV-40542 MSAN use-of-uninitialized-value on Unknown_log_event::read_checksum_alg
-
- Open
-