darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

step-over-trips-on-watchpoint.exp: Don't put addresses in test messages

Browse source 
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.
This commit is contained in:
Pedro Alves 2015-04-10 19:23:24 +01:00
parent f74839702e
commit 07473109e1
2 changed files with 10 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gdb/testsuite/ChangeLog
View file

@ -1,3 +1,8 @@
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

7
gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.exp
View file

@ -96,7 +96,8 @@ proc do_test { displaced with_bp } {
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"
@ -105,7 +106,9 @@ proc do_test { displaced with_bp } {
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.