Diffing test results, I noticed:
-PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: b *0x0000000000400811 thread 1
+PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: b *0x00000000004007d1 thread 1
gdb/testsuite/ChangeLog:
2015-04-10 Pedro Alves <palves@redhat.com>
* gdb.threads/step-over-trips-on-watchpoint.exp (do_test): Use
test messages that don't include the breakpoint address.
+2015-04-10 Pedro Alves <palves@redhat.com>
+
+ * gdb.threads/step-over-trips-on-watchpoint.exp (do_test): Use
+ test messages that don't include the breakpoint address.
+
2015-04-10 Yao Qi <yao.qi@linaro.org>
* gdb.base/watchpoint-reuse-slot.exp (valid_addr_p): Return
delete_breakpoints
}
- gdb_breakpoint "*$address_triggers_watch"
+ gdb_test "break *$address_triggers_watch" "Breakpoint .*" \
+ "set breakpoint at address that triggers watch"
gdb_continue_to_breakpoint \
"run to instruction that triggers watch in thread 2"
gdb_test "watch watch_me" "Hardware watchpoint .*"
if ${with_bp} {
- gdb_test "b *$after_address_triggers_watch thread 1"
+ gdb_test "b *$after_address_triggers_watch thread 1" \
+ "Breakpoint .*" \
+ "set breakpoint specific to thread 1"
}
# Switch back to thread 1 and disable scheduler locking.