summaryrefslogtreecommitdiff
path: root/gdb/testsuite
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2015-08-06 18:22:57 +0100
committerPedro Alves <palves@redhat.com>2015-08-07 17:26:20 +0100
commitd55007b58352c0b5fd2817e003b6dcf4e3ee4c07 (patch)
tree81f6012e3afcd63f51152e8f12e6bda580337026 /gdb/testsuite
parentfbea99ea8a062e5cd96e2d88336984ed3adc93d4 (diff)
downloadbinutils-gdb-d55007b58352c0b5fd2817e003b6dcf4e3ee4c07.tar.gz
Fix signal-while-stepping-over-bp-other-thread.exp on targets always in non-stop
With "maint set target-non-stop on" we get: -PASS: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step +FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step The issue is simply that switch_back_to_stepped_thread is not used in non-stop mode, thus infrun doesn't output the expected "switching back to stepped thread" log. gdb/testsuite/ChangeLog: 2015-08-07 Pedro Alves <palves@redhat.com> * signal-while-stepping-over-bp-other-thread.exp: Expect "restart threads" as alternative to "switching back to stepped thread".
Diffstat (limited to 'gdb/testsuite')
-rw-r--r--gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp b/gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp
index 3201b1f36e0..371395183ca 100644
--- a/gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp
+++ b/gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp
@@ -100,7 +100,7 @@ gdb_test_sequence $test $test {
"need to step-over"
"resume \\(step=1"
"signal arrived while stepping over breakpoint"
- "switching back to stepped thread"
+ "(restart threads|switching back to stepped thread)"
"stepped to a different line"
"callme"
}