Source: mariadb
Version: 1:10.11.5-1
Tags: upstream, confirmed, help, ftbfs
X-Debbugs-CC: debian-sparc@lists.debian.org
User: debian-sparc@lists.debian.org
Usertags: sparc64
Builds on sparc64 repeatedly failed on tests main.ctype_binary
main.ctype_latin1 with error message:
main.ctype_binary w13 [ fail ]
Test ended at 2023-10-04 07:23:33
CURRENT_TEST: main.ctype_binary
mysqltest: At line 209: query 'SELECT COUNT(*) FROM t WHERE
EXTRACTVALUE(c,'a')='a'' failed: <Unknown> (2013): Lost connection to
server during query
..
Thread 1 (Thread 0xffff8001022f68c0 (LWP 508035)):
#0 0xffff8001026918f8 in ?? () from /lib/sparc64-linux-gnu/libc.so.6
No symbol table info available.
#1 0x0000010000a18920 in handle_fatal_signal (sig=10) at
./sql/signal_handler.cc:360
curr_time = 1696404205
tm = {tm_sec = 25, tm_min = 23, tm_hour = 7, tm_mday = 4,
tm_mon = 9, tm_year = 123, tm_wday = 3, tm_yday = 276, tm_isdst = 0,
tm_gmtoff = 0, tm_zone = 0x100022e69e0 "UTC"}
thd = 0xffff80011c000c68
print_invalid_query_pointer = false
Backtrace stopped: Cannot access memory at address 0xf0
This indicates that the code path in these two tests are able to crash
the server.
Full logs with full stack trace at:
*
https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=sparc64&ver=1%3A10.11.5-1&stamp=1696405551&raw=0
*
https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=sparc64&ver=1%3A10.11.5-1&stamp=1696474965&raw=0
These two tests were passing in the 10.11.4-1 builds in Debian
unstable, so this is clearly a regression in 10.11.5.
