[MDEV-12053] mysqltest crashes in vio_description / .. / mysql_read_query_result, innodb.innodb-blob with ps-protocol fails in buildbot and outside Created: 2017-02-12  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Scripts & Clients, Tests
Affects Version/s: 10.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-7069 Fix buildbot failures in main server ... Stalled

 Description   

Apparently the failure started happening in buildbot from this push:
https://internal.askmonty.org/buildbot/builders/kvm-fulltest2/builds/7058

Reproducible outisde the buildbot as well.

$ perl ./mtr innodb.innodb-blob --ps-protocol
...
 
Thread 1 (Thread 0x7f898fe20740 (LWP 29514)):
#0  0x00007f898f5c8101 in __pthread_kill (threadid=<optimized out>, signo=11) at ../nptl/sysdeps/unix/sysv/linux/pthread_kill.c:61
#1  0x00007f898fa89344 in my_write_core (sig=11) at /data/src/10.1/mysys/stacktrace.c:477
#2  0x00007f898fa4ae63 in signal_handler (sig=11) at /data/src/10.1/client/mysqltest.cc:8817
#3  <signal handler called>
#4  0x00007f898fa852cf in vio_description (vio=0x0) at /data/src/10.1/vio/viosocket.c:640
#5  0x00007f898fa630b8 in cli_safe_read (mysql=0x7f899168a480) at /data/src/10.1/sql-common/client.c:585
#6  0x00007f898fa6abb9 in cli_read_query_result (mysql=0x7f899168a480) at /data/src/10.1/sql-common/client.c:3993
#7  0x00007f898fa5f53b in mysql_read_query_result (mysql=0x7f899168a480) at /data/src/10.1/libmysql/libmysql.c:4908
#8  0x00007f898fa39793 in wrap_mysql_read_query_result (mysql=0x7f899168a480) at /data/src/10.1/client/../tests/nonblock-wrappers.h:360
#9  0x00007f898fa48c28 in run_query_normal (cn=0x7f8991685670, command=0x7f89916d8bd0, flags=2, query=0x7f89916d8d50 "reap", query_len=4, ds=0x7f8990008860 <ds_res>, ds_warnings=0x7ffc08f2c7a0) at /data/src/10.1/client/mysqltest.cc:7763
#10 0x00007f898fa4a4ac in run_query (cn=0x7f8991685670, command=0x7f89916d8bd0, flags=2) at /data/src/10.1/client/mysqltest.cc:8526
#11 0x00007f898fa4c1cc in main (argc=13, argv=0x7ffc08f2cb98) at /data/src/10.1/client/mysqltest.cc:9306



 Comments   
Comment by Marko Mäkelä [ 2017-05-16 ]

I think that this is unrelated to the InnoDB test and code changes that I made in the push that was identified above.
The only code change is a minor change to InnoDB startup.
The stack trace looks like it is from the mysqltest client program, not from the server at all.

On a related note, mysqltest reports a memory leak for the following:

perl;
die
EOF

Generated at Thu Feb 08 07:54:45 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.