Avoid unstable test message in gdb.base/step-over-exit.exp

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.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 499377b..ad33192 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -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.

diff --git a/gdb/testsuite/gdb.base/step-over-exit.exp b/gdb/testsuite/gdb.base/step-over-exit.exp
index c921dcc..1e00010 100644 (file)
--- a/gdb/testsuite/gdb.base/step-over-exit.exp
+++ b/gdb/testsuite/gdb.base/step-over-exit.exp
@@ -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.