[PATCH v3 11/17] Fix signal-while-stepping-over-bp-other-thread.exp on targets always in non-stop

Pedro Alves
2015-04-17T10:45:38Z

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-04-17 Pedro Alves <palves@redhat.com>

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

v3:

- Cleanups were moved to a separate patch and pushed already. Now a
one-liner. Also, v2 mentioned the wrong output by silly
mistake....
---
.../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"
"callme"
}
--
1.9.3