From 4562af4aed5a99076ae2da8d4c28100659214fc1 Mon Sep 17 00:00:00 2001 From: Jakub Nowakowski Date: Wed, 2 Sep 2026 14:42:54 +0200 Subject: [PATCH] PXB-2553: Fix stacktrace assertion in bug766305 test https://perconadev.atlassian.net/browse/PXB-2553 Problem: -------- The test sends SIGSEGV to xtrabackup and verifies a resolved stack trace is produced. The assertion grepped for "handle_fatal_signal", which only appears when the signal handler frame is resolved as a symbol in the backtrace. This is platform- and compiler-dependent: the signal is delivered to an arbitrary thread, and the backtrace shows that thread's stack, not the signal handler's frame. Fix: ---- Replace the assertion with a regex matching any resolved stack frame with a source location ("... at ..."), which is always present regardless of which thread receives the signal. --- storage/innobase/xtrabackup/test/t/bug766305.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/storage/innobase/xtrabackup/test/t/bug766305.sh b/storage/innobase/xtrabackup/test/t/bug766305.sh index d5d5e534aa31..1366ae5b8afa 100644 --- a/storage/innobase/xtrabackup/test/t/bug766305.sh +++ b/storage/innobase/xtrabackup/test/t/bug766305.sh @@ -29,5 +29,5 @@ kill -SIGCONT $xb_pid run_cmd_expect_failure wait $job_pid -grep -q "handle_fatal_signal" $OUTFILE || \ +grep -qE "#[0-9]+ 0x[0-9a-f]+ .+ at " $OUTFILE || \ die "Could not find a resolved stacktrace in the log"