[12/18] Fix signal-while-stepping-over-bp-other-thread.exp on targets always in non-stop

Message ID 1432250354-2721-13-git-send-email-palves@redhat.com
State New, archived

Commit Message

Pedro Alves May 21, 2015, 11:19 p.m. UTC
  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.

2015-05-21  Pedro Alves  <palves@redhat.com>

	* signal-while-stepping-over-bp-other-thread.exp: Expect "restart
	threads" as alternative to "switching back to stepped thread".


  - no changes.


  - Cleanups were moved to a separate patch and pushed already.  Now a
    one-liner.  Also, v2 mentioned the wrong output by silly
 .../gdb.threads/signal-while-stepping-over-bp-other-thread.exp          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


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 3201b1f..3713951 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"