[gdb/testsuite] Fix gdb.threads/killed-outside.exp on aarch64
authorTom de Vries <tdevries@suse.de>
Fri, 29 Jul 2022 06:49:45 +0000 (08:49 +0200)
committerTom de Vries <tdevries@suse.de>
Fri, 29 Jul 2022 06:49:45 +0000 (08:49 +0200)
commitb245c595aaa59812f8f3a0e8b70ea5f52e045627
tree9f6f88260e909ee4c583a1674e8583280c68c493
parentf8ad70a17bfc12199cc5a20b55b369c3dfa6cb42
[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