Fix signal-while-stepping-over-bp-other-thread.exp on targets always in non-stop
authorPedro Alves <palves@redhat.com>
Thu, 6 Aug 2015 17:22:57 +0000 (18:22 +0100)
committerPedro Alves <palves@redhat.com>
Fri, 7 Aug 2015 16:26:20 +0000 (17:26 +0100)
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".

gdb/ChangeLog
gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp

index 11a60d477e5b219940c7c5883c8b4181b3b59e65..6bab8fad9e374fbae85bfb1976de6e288cc0e595 100644 (file)
@@ -1,3 +1,8 @@
+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".
+
 2015-08-07  Pedro Alves  <palves@redhat.com>
 
        * NEWS: Mention "maint set/show target-non-stop".
index 3201b1f36e048e32bb6f307104974693fbb3fa70..371395183ca77ed5029db07b59752afe338b2d9f 100644 (file)
@@ -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"
 }