Avoid unstable test message in gdb.base/step-over-exit.exp
authorPedro Alves <palves@redhat.com>
Wed, 8 Mar 2017 22:05:36 +0000 (22:05 +0000)
committerPedro Alves <palves@redhat.com>
Wed, 8 Mar 2017 22:05:36 +0000 (22:05 +0000)
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
gdb/testsuite/gdb.base/step-over-exit.exp

index 499377bd7373ad5ea29326f1c98b2b82e4e33868..ad33192ff6448fb9e07f247e930385d6da9ed8f4 100644 (file)
@@ -1,3 +1,7 @@
+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
index c921dcc3e5b5bb0cef9b68fb08754c1c636ae72e..1e00010ec85cd3f772f461c0dc1ad1209dadf242 100644 (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.