[pushed] Avoid unstable test message in gdb.base/step-over-exit.exp
Commit Message
Currently diffing testrun results shows:
-PASS: gdb.base/step-over-exit.exp: break *0x7ffff77e18c6 if main == 0
+PASS: gdb.base/step-over-exit.exp: break *0x2aaaab0988c6 if main == 0
gdb/testsuite/ChangeLog:
2017-03-08 Pedro Alves <palves@redhat.com>
* gdb.base/step-over-exit.exp: Add explicit test message.
---
gdb/testsuite/ChangeLog | 4 ++++
gdb/testsuite/gdb.base/step-over-exit.exp | 3 ++-
2 files changed, 6 insertions(+), 1 deletion(-)
@@ -1,5 +1,9 @@
2017-03-08 Pedro Alves <palves@redhat.com>
+ * gdb.base/step-over-exit.exp: Add explicit test message.
+
+2017-03-08 Pedro Alves <palves@redhat.com>
+
PR gdb/18360
* gdb.threads/interrupt-while-step-over.c: New file.
* gdb.threads/interrupt-while-step-over.exp: New file.
@@ -111,7 +111,8 @@ gdb_test_multiple $test $test {
}
gdb_test "break \*$syscall_insn_addr if main == 0" \
- "Breakpoint \[0-9\]* at .*"
+ "Breakpoint \[0-9\]* at .*" \
+ "set conditional break at syscall address"
# Resume the child process, and the step-over is being done.