aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSandra Loosemore <sandra@codesourcery.com>2023-09-05 18:48:22 +0000
committerSandra Loosemore <sandra@codesourcery.com>2023-09-05 18:48:22 +0000
commita006bc9c37e95b4afaf85715cc54fe57b3300ccd (patch)
treee9feaf2108e815ef4ade82721dd1c6cb4f21f316
parent8de9b683a5ff28e3370777ed4396a14093910fc2 (diff)
downloadbinutils-a006bc9c37e95b4afaf85715cc54fe57b3300ccd.zip
binutils-a006bc9c37e95b4afaf85715cc54fe57b3300ccd.tar.gz
binutils-a006bc9c37e95b4afaf85715cc54fe57b3300ccd.tar.bz2
gdb/testsuite: Make hook-stop.exp ignore termination message from GDB stub
When a GDB stub is run via "target remote |", it sometimes produces extra output that ends up mixed with GDB's own output. For example, QEMU's built-in GDB stub responds to the vKill packet by printing nios2-elf-qemu-system: QEMU: Terminated via GDBstub before exiting. This patch fixes the regexp in gdb.base/hook-stop.exp to allow such messages between GDB's "continuing" and "Inferior killed" messages. Reviewed-By: Tom Tromey <tom@tromey.com> Approved-By: Tom Tromey <tom@tromey.com>
-rw-r--r--gdb/testsuite/gdb.base/hook-stop.exp2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.base/hook-stop.exp b/gdb/testsuite/gdb.base/hook-stop.exp
index 0babd46..50c5dfe 100644
--- a/gdb/testsuite/gdb.base/hook-stop.exp
+++ b/gdb/testsuite/gdb.base/hook-stop.exp
@@ -85,7 +85,7 @@ proc hook_stop_kill {} {
set test "run hook-stop"
gdb_test_multiple "continue" "$test" {
- -re "Continuing.\r\n\\\[Inferior $decimal \\(.*\\) killed\\\]\r\n${gdb_prompt} $" {
+ -re "Continuing.*\r\n\\\[Inferior $decimal \\(.*\\) killed\\\]\r\n${gdb_prompt} $" {
pass $test
}
}