[MDEV-22936] Assertion `m_curr_row <= m_rows_end' failed in Rows_log_event::unpack_current_row (debug) | ERROR 1105 (HY000): Unknown error (optimized builds) | Got error 171 "The event was corrupt, leading to illegal data being read Created: 2020-06-18  Updated: 2023-11-28

Status: Confirmed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.1, 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9, 10.10, 10.11, 11.0, 11.1
Fix Version/s: 10.4, 10.5, 10.6, 10.11, 11.1

Type: Bug Priority: Major
Reporter: Roel Van de Paar Assignee: Andrei Elkin
Resolution: Unresolved Votes: 0
Labels: affects-tests


 Description   

Note: --log-bin option is not required.

USE test;
 
BINLOG 'AMqaOw8BAAAAdAAAAHgAAAAAAAQANS42LjM0LTc5LjEtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAYVx w2w=';
 
CREATE TABLE t1 (c INT);
 
BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';

Leads to:

10.5.4 4080e3acefd7e58d88c2f3539fb6a0fb359cf057

 
mysqld: /test/10.5_dbg/sql/log_event.h:5186: int Rows_log_event::unpack_current_row(rpl_group_info*): Assertion `m_curr_row <= m_rows_end' failed.

10.5.4 4080e3acefd7e58d88c2f3539fb6a0fb359cf057

 
Core was generated by `/test/MD150620-mariadb-10.5.4-linux-x86_64-dbg/bin/mysqld --no-defaults --core-'.
 
Program terminated with signal SIGABRT, Aborted.
 
#0  __pthread_kill (threadid=<optimized out>, signo=signo@entry=6)
 
    at ../sysdeps/unix/sysv/linux/pthread_kill.c:57
 
[Current thread is 1 (Thread 0x14d1458b5700 (LWP 4107605))]
 
(gdb) bt
 
#0  __pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ../sysdeps/unix/sysv/linux/pthread_kill.c:57
 
#1  0x000055fda8ff24c6 in my_write_core (sig=sig@entry=6) at /test/10.5_dbg/mysys/stacktrace.c:518
 
#2  0x000055fda8794d60 in handle_fatal_signal (sig=6) at /test/10.5_dbg/sql/signal_handler.cc:330
 
#3  <signal handler called>
 
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
 
#5  0x000014d146729801 in __GI_abort () at abort.c:79
 
#6  0x000014d14671939a in __assert_fail_base (fmt=0x14d1468a07d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x55fda9335456 "m_curr_row <= m_rows_end", file=file@entry=0x55fda914e080 "/test/10.5_dbg/sql/log_event.h", line=line@entry=5186, function=function@entry=0x55fda93386c0 <Rows_log_event::unpack_current_row(rpl_group_info*)::__PRETTY_FUNCTION__> "int Rows_log_event::unpack_current_row(rpl_group_info*)") at assert.c:92
 
#7  0x000014d146719412 in __GI___assert_fail (assertion=assertion@entry=0x55fda9335456 "m_curr_row <= m_rows_end", file=file@entry=0x55fda914e080 "/test/10.5_dbg/sql/log_event.h", line=line@entry=5186, function=function@entry=0x55fda93386c0 <Rows_log_event::unpack_current_row(rpl_group_info*)::__PRETTY_FUNCTION__> "int Rows_log_event::unpack_current_row(rpl_group_info*)") at assert.c:101
 
#8  0x000055fda8900539 in Rows_log_event::unpack_current_row (rgi=0x14d125c8d800, this=0x14d125cff288) at /test/10.5_dbg/sql/log_event.h:5186
 
#9  Rows_log_event::write_row (this=this@entry=0x14d125cff288, rgi=rgi@entry=0x14d125c8d800, overwrite=false) at /test/10.5_dbg/sql/log_event_server.cc:7196
 
#10 0x000055fda8901452 in Write_rows_log_event::do_exec_row (this=0x14d125cff288, rgi=0x14d125c8d800) at /test/10.5_dbg/sql/log_event_server.cc:7482
 
#11 0x000055fda88f2223 in Rows_log_event::do_apply_event (this=0x14d125cff288, rgi=0x14d125c8d800) at /test/10.5_dbg/sql/log_event_server.cc:5652
 
#12 0x000055fda861152d in Log_event::apply_event (rgi=0x14d125c8d800, this=0x14d125cff288) at /test/10.5_dbg/sql/log_event.h:1496
 
#13 mysql_client_binlog_statement (thd=thd@entry=0x14d125c15088) at /test/10.5_dbg/sql/sql_binlog.cc:357
 
#14 0x000055fda84ef4de in mysql_execute_command (thd=thd@entry=0x14d125c15088) at /test/10.5_dbg/sql/sql_parse.cc:5865
 
#15 0x000055fda84f715c in mysql_parse (thd=thd@entry=0x14d125c15088, rawbuf=<optimized out>, length=<optimized out>, parser_state=parser_state@entry=0x14d1458b4350, is_com_multi=is_com_multi@entry=false, is_next_command=is_next_command@entry=false) at /test/10.5_dbg/sql/sql_parse.cc:7993
 
#16 0x000055fda84e3c60 in dispatch_command (command=command@entry=COM_QUERY, thd=thd@entry=0x14d125c15088, packet=packet@entry=0x14d125c67089 "BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA='", packet_length=packet_length@entry=118, is_com_multi=is_com_multi@entry=false, is_next_command=is_next_command@entry=false) at /test/10.5_dbg/sql/sql_parse.cc:1874
 
#17 0x000055fda84e243a in do_command (thd=0x14d125c15088) at /test/10.5_dbg/sql/sql_parse.cc:1355
 
#18 0x000055fda863dc47 in do_handle_one_connection (connect=<optimized out>, connect@entry=0x14d127d7a808, put_in_cache=put_in_cache@entry=true) at /test/10.5_dbg/sql/sql_connect.cc:1411
 
#19 0x000055fda863e363 in handle_one_connection (arg=arg@entry=0x14d127d7a808) at /test/10.5_dbg/sql/sql_connect.cc:1313
 
#20 0x000055fda8a9f902 in pfs_spawn_thread (arg=0x14d145046c88) at /test/10.5_dbg/storage/perfschema/pfs.cc:2201
 
#21 0x000014d14740c6db in start_thread (arg=0x14d1458b5700) at pthread_create.c:463
 
#22 0x000014d14680a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Bug confirmed present in:
MariaDB: 10.1.46 (dbg), 10.2.33 (dbg), 10.3.24 (dbg), 10.4.14 (dbg), 10.5.4 (dbg)

Bug confirmed not present in:
MariaDB: 10.1.46 (opt), 10.2.33 (opt), 10.3.24 (opt), 10.4.14 (opt), 10.5.4 (opt)
MySQL: 5.5.62 (dbg), 5.5.62 (opt), 5.6.47 (dbg), 5.6.47 (opt), 5.7.29 (dbg), 5.7.29 (opt), 8.0.19 (dbg), 8.0.19 (opt)

 Comments   
Comment by Roel Van de Paar [ 2020-06-19 ]

Variation 1: t1 does not exist (changed table name)

10.5.4 4080e3acefd7e58d88c2f3539fb6a0fb359cf057

 
10.5.4>USE test;
 
Database changed
 
10.5.4>BINLOG 'AMqaOw8BAAAAdAAAAHgAAAAAAAQANS42LjM0LTc5LjEtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAYVx w2w=';
 
Query OK, 0 rows affected (0.001 sec)
 
10.5.4>CREATE TABLE t2 (c INT);
 
Query OK, 0 rows affected (0.017 sec)
 
10.5.4>BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';
 
ERROR 1146 (42S02): *Table 'test.t1' doesn't exist*

Variation 2: ERROR 1105 (HY000): Uknown error (changed table def)

10.5.4 4080e3acefd7e58d88c2f3539fb6a0fb359cf057

 
10.5.4>USE test;
 
Database changed
 
10.5.4>BINLOG 'AMqaOw8BAAAAdAAAAHgAAAAAAAQANS42LjM0LTc5LjEtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAYVx w2w=';
 
Query OK, 0 rows affected (0.000 sec)
 
10.5.4>CREATE TABLE t1 (a MEDIUMBLOB, b MEDIUMBLOB, c BIGINT PRIMARY KEY);
 
Query OK, 0 rows affected (0.014 sec)
 
10.5.4>BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';
 
ERROR 1105 (HY000): Unknown error

ERROR 1105 (HY000): Unknown error in variation 2 is also reproducible on optimized builds:

10.5.4 4080e3acefd7e58d88c2f3539fb6a0fb359cf057 (opt)

 
10.5.4>USE test;
 
Database changed
 
10.5.4>BINLOG 'AMqaOw8BAAAAdAAAAHgAAAAAAAQANS42LjM0LTc5LjEtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAYVx w2w=';
 
Query OK, 0 rows affected (0.001 sec)
 
10.5.4>CREATE TABLE t1 (a MEDIUMBLOB, b MEDIUMBLOB, c BIGINT PRIMARY KEY);
 
Query OK, 0 rows affected (0.017 sec)
 
10.5.4>BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';
 
ERROR 1105 (HY000): Unknown error

Comment by Sachin Setiya (Inactive) [ 2020-06-22 ]

Hi Roel

I tried this variation 

USE test;
 
BINLOG 'AMqaOw8BAAAAdAAAAHgAAAAAAAQANS42LjM0LTc5LjEtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAYVx w2w=';
 
CREATE TABLE t1 (c INT, d int);
 
BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';
 



BINLOG 'AMqaOw8BAAAAdAAAAHgAAAAAAAQANS42LjM0LTc5LjEtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAYVx w2w=';
 
CREATE TABLE t1 (c INT, d int);
 
BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';
 
main.tmp                                 [ fail ]
 
        Test ended at 2020-06-22 21:51:36
 
 
 
CURRENT_TEST: main.tmp
 
mysqltest: At line 7: query 'BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA='' failed: 1030: Got error 171 "The event was corrupt, leading to illegal data being read" from storage engine MyISAM

To me binlog looks corrupt
Can you please update the test case with commands which generated the binlog

Comment by Roel Van de Paar [ 2020-07-21 ]

Hi sachin.setiya.007. I did not generate those statements; they were taken from an MTR test. I cannot locate which one, in spite of an extensive search. Irrespective where they came from though, these statements crash/error the server in various ways as described.

I also tried to convert the entries back to normal SQL commands using `mysqlbinlog --base64-output=decode-rows -vv`, but as the binlog format is binary which does not allow editing (and the commands are BINLOG commands already), this was not possible.

Also, the fact that the second command does not fail in variation 1 means it is at least partially interpreted as referring to t1. Perhaps gdb or strace may assist in shedding some more light. Final thought; even if the log were corrupt, the server should be able handle the corruption?

Comment by Roel Van de Paar [ 2023-01-13 ]

Replaying the testcase against an optimized build (but not debug), InnoDB reports the event as being corrupt:

11.0.1 b075191ba8598af6aff5549e6e19f6255aef258a (Optimized)

 
11.0.1-opt>USE test;
 
Database changed
 
11.0.1-opt>BINLOG 'AMqaOw8BAAAAdAAAAHgAAAAAAAQANS42LjM0LTc5LjEtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAYVx w2w=';
 
Query OK, 0 rows affected (0.000 sec)
 
 
 
11.0.1-opt>CREATE TABLE t1 (c INT);
 
Query OK, 0 rows affected (0.009 sec)
 
 
 
11.0.1-opt>BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';
 
ERROR 1030 (HY000): Got error 171 "The event was corrupt, leading to illegal data being read" from storage engine InnoDB

Comment by Roel Van de Paar [ 2023-02-03 ]

Related to this, 

CREATE TABLE t1(a INT);
 
FLUSH TABLES WITH READ LOCK;
 
BINLOG ' SOgWTg8CAAAAbgAAAHIAAAAAAAQANS42LjMtbTUtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAABI6BZOEzgNAAgAEgAEBAQEEgAAVgAEGggAAAAICAgCAAAAAAVAYI8=';
 
BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';

Produces:

11.0.1 b075191ba8598af6aff5549e6e19f6255aef258a (Optimized)

 
2023-02-04 10:37:50 4 [ERROR]  BINLOG_BASE64_EVENT: Error executing row event: 'Can't execute the query because you have a conflicting read lock', Internal MariaDB error code: 1223

Comment by Roel Van de Paar [ 2023-06-26 ]

Various other testcases seen in connection with similar errors (including MariaDB error code: 1030 and 1610 and Got error 171)

# mysqld options required for replay:  --sql_mode=
 
BINLOG 'AMqaOw8BAAAAdAAAAHgAAAAAAAQANS42LjM0LTc5LjEtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAYVx w2w=';
 
CREATE TABLE t1(a INT KEY,b INT)ENGINE=Spider;
 
BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';


CREATE TABLE t1(a1 INT,a2 INT);
 
BINLOG ' mSKWVg8BAAAAdwAAAHsAAAAAAAQANS44LjAtbTE3LWRlYnVnLWxvZwAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAACZIpZWEzgNAAgAEgAEBAQEEgAAXwAEGggAAAAICAgCAAAACgoKKioAEjQA AYzz6oU=';
 
SET lc_messages=ru_RU;
 
BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';


SET SESSION max_error_count=0;   
BINLOG ' mSKWVg8BAAAAdwAAAHsAAAAAAAQANS44LjAtbTE3LWRlYnVnLWxvZwAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAACZIpZWEzgNAAgAEgAEBAQEEgAAXwAEGggAAAAICAgCAAAACgoKKioAEjQA AYzz6oU=';
 
CREATE TABLE t1(c INT);
 
BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';


CREATE TABLE t1(f INT KEY)ENGINE=MyISAM;
 
BINLOG 'AMqaOw8BAAAAdAAAAHgAAAAAAAQANS42LjM0LTc5LjEtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAYVx w2w=';
 
BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';

Comment by Ramesh Sivaraman [ 2023-11-14 ]

Another test case with slightly different stack. 

CREATE TABLE t1(i INT);
 
set @@global.slave_exec_mode='IDEMPOTENT';
 
BINLOG ' SOgWTg8BAAAAbgAAAHIAAAAAAAQANS42LjMtbTUtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAABI6BZOEzgNAAgAEgAEBAQEEgAAVgAEGggAAAAICAgCAAAAAAVAYI8=';
 
binlog 'bBf2ZBMBAAAANAAAAHUkAAAAAHEAAAAAAAEABHRlc3QAAnQxAAQDDw8IBP0C4h0AaTGFIg==bBf2ZBgBAAAASAAAAL0kAAAAAHEAAAAAAAEABP//8I+kAAABAGIBAGWuv1VNCQAAAPBuWwAAAQBiAQBlrr9VTQkAAADxS9Lu';

Leads to

10.4.32 f7552313d4e54a1cbfa5cb9bb9d06a55df7d0e95 (Debug)

 
mariadbd: /test/mtest/10.4_dbg/sql/log_event.h:4684: int Rows_log_event::unpack_current_row(rpl_group_info*, const MY_BITMAP*): Assertion `m_curr_row <= m_rows_end' failed.

10.4.32 f7552313d4e54a1cbfa5cb9bb9d06a55df7d0e95 (Debug)

 
Core was generated by `/test/mtest/MD111123-mariadb-10.4.32-linux-x86_64-dbg/bin/mariadbd --no-default'.
 
Program terminated with signal SIGABRT, Aborted.
 
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 
[Current thread is 1 (Thread 0x15327432a700 (LWP 3350850))]
 
(gdb) bt
 
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 
#1  0x0000153275773859 in __GI_abort () at abort.c:79
 
#2  0x0000153275773729 in __assert_fail_base (fmt=0x153275909588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x563196e46f73 "m_curr_row <= m_rows_end", file=0x563196ca5320 "/test/mtest/10.4_dbg/sql/log_event.h", line=4684, function=<optimized out>) at assert.c:92
 
#3  0x0000153275784fd6 in __GI___assert_fail (assertion=assertion@entry=0x563196e46f73 "m_curr_row <= m_rows_end", file=file@entry=0x563196ca5320 "/test/mtest/10.4_dbg/sql/log_event.h", line=line@entry=4684, function=function@entry=0x563196e461b8 "int Rows_log_event::unpack_current_row(rpl_group_info*, const MY_BITMAP*)") at assert.c:101
 
#4  0x000056319644cb9a in Rows_log_event::unpack_current_row (cols=0x1532005864f8, rgi=0x15320071c700, this=0x153200586458) at /test/mtest/10.4_dbg/sql/log_event.h:4684
 
#5  Update_rows_log_event::do_exec_row (this=0x153200586458, rgi=0x15320071c700) at /test/mtest/10.4_dbg/sql/log_event.cc:14807
 
#6  0x000056319643b7a7 in Rows_log_event::do_apply_event (this=0x153200586458, rgi=0x15320071c700) at /test/mtest/10.4_dbg/sql/log_event.cc:11681
 
#7  0x00005631961441bf in Log_event::apply_event (rgi=0x15320071c700, this=0x153200586458) at /test/mtest/10.4_dbg/sql/log_event.h:1492
 
#8  mysql_client_binlog_statement (thd=thd@entry=0x153200000d28) at /test/mtest/10.4_dbg/sql/sql_binlog.cc:355
 
#9  0x0000563196033d6c in mysql_execute_command (thd=thd@entry=0x153200000d28) at /test/mtest/10.4_dbg/sql/sql_parse.cc:6137
 
#10 0x00005631960366ca in mysql_parse (thd=thd@entry=0x153200000d28, rawbuf=<optimized out>, length=<optimized out>, parser_state=parser_state@entry=0x153274329360, is_com_multi=is_com_multi@entry=false, is_next_command=is_next_command@entry=false) at /test/mtest/10.4_dbg/sql/sql_parse.cc:8014
 
#11 0x00005631960396de in dispatch_command (command=command@entry=COM_QUERY, thd=thd@entry=0x153200000d28, packet=packet@entry=0x153200019749 "binlog 'bBf2ZBMBAAAANAAAAHUkAAAAAHEAAAAAAAEABHRlc3QAAnQxAAQDDw8IBP0C4h0AaTGFIg==bBf2ZBgBAAAASAAAAL0kAAAAAHEAAAAAAAEABP//8I+kAAABAGIBAGWuv1VNCQAAAPBuWwAAAQBiAQBlrr9VTQkAAADxS9Lu';", packet_length=packet_length@entry=178, is_com_multi=is_com_multi@entry=false, is_next_command=is_next_command@entry=false) at /test/mtest/10.4_dbg/sql/sql_class.h:1242
 
#12 0x000056319603c347 in do_command (thd=0x153200000d28) at /test/mtest/10.4_dbg/sql/sql_parse.cc:1378
 
#13 0x0000563196167b46 in do_handle_one_connection (connect=connect@entry=0x56319a3f0198) at /test/mtest/10.4_dbg/sql/sql_connect.cc:1419
 
#14 0x0000563196167c65 in handle_one_connection (arg=0x56319a3f0198) at /test/mtest/10.4_dbg/sql/sql_connect.cc:1323
 
#15 0x0000153275c84609 in start_thread (arg=<optimized out>) at pthread_create.c:477
 
#16 0x0000153275870133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Generated at Thu Feb 08 09:18:36 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.