From b245c595aaa59812f8f3a0e8b70ea5f52e045627 Mon Sep 17 00:00:00 2001 From: Tom de Vries Date: Fri, 29 Jul 2022 08:49:45 +0200 Subject: [PATCH] [gdb/testsuite] Fix gdb.threads/killed-outside.exp on aarch64 On aarch64 (and likewise on arm), I run into: ... (gdb) PASS: gdb.threads/killed-outside.exp: get pid of inferior Executing on target: kill -9 11516 (timeout = 300) builtin_spawn -ignore SIGHUP kill -9 11516^M continue^M Continuing.^M Unable to fetch general registers: No such process.^M (gdb) [Thread 0xfffff7d511e0 (LWP 11518) exited]^M ^M Program terminated with signal SIGKILL, Killed.^M The program no longer exists.^M FAIL: gdb.threads/killed-outside.exp: prompt after first continue (timeout) ... due to a mismatch between the actual "No such process" line and the expected one: ... set no_such_process_msg "Couldn't get registers: No such process\." ... Fix this by updating the regexp. Tested on aarch64-linux, and x86_64-linux. --- gdb/testsuite/gdb.threads/killed-outside.exp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gdb/testsuite/gdb.threads/killed-outside.exp b/gdb/testsuite/gdb.threads/killed-outside.exp index 3d4543e088c..7fa6b26c685 100644 --- a/gdb/testsuite/gdb.threads/killed-outside.exp +++ b/gdb/testsuite/gdb.threads/killed-outside.exp @@ -37,7 +37,8 @@ remote_exec target "kill -9 ${testpid}" # Give it some time to die. sleep 2 -set no_such_process_msg "Couldn't get registers: No such process\." +set regs_msg "(Couldn't get registers|Unable to fetch general registers)" +set no_such_process_msg "$regs_msg: No such process\." set killed_msg "Program terminated with signal SIGKILL, Killed\." set no_longer_exists_msg "The program no longer exists\." set not_being_run_msg "The program is not being run\." -- 2.30.2