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

Cleanup signal-while-stepping-over-bp-other-thread.exp

Browse source 
gdb/testsuite/ChangeLog:
2015-04-10  Pedro Alves  <palves@redhat.com>

	* gdb.threads/signal-while-stepping-over-bp-other-thread.exp: Use
	gdb_test_sequence and gdb_assert.
This commit is contained in:
Pedro Alves 2015-03-09 19:02:30 +00:00
parent 07473109e1
commit 9ee417720b
2 changed files with 15 additions and 10 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/signal-while-stepping-over-bp-other-thread.exp: Use
gdb_test_sequence and gdb_assert.
2015-04-10 Pedro Alves <palves@redhat.com>
* gdb.threads/step-over-trips-on-watchpoint.exp (do_test): Use

20
gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp
View file

@ -95,19 +95,19 @@ gdb_test "set scheduler-locking off"
# Make sure we're exercising the paths we want to.
gdb_test "set debug infrun 1"
gdb_test \
"step" \
".*need to step-over.*resume \\(step=1.*signal arrived while stepping over breakpoint.*switching back to stepped thread.*stepped to a different line.*callme.*" \
"step"
set test "step"
gdb_test_sequence $test $test {
"need to step-over"
"resume \\(step=1"
"signal arrived while stepping over breakpoint"
"switching back to stepped thread"
"stepped to a different line"
"callme"
}
set cnt_after [get_value "args\[$my_number\]" "get count after step"]
# Test that GDB doesn't inadvertently resume the stepped thread when a
# signal arrives while stepping over a breakpoint in another thread.
set test "stepped thread under control"
if { $cnt_before + 1 == $cnt_after } {
pass $test
} else {
fail $test
}
gdb_assert { $cnt_before + 1 == $cnt_after } "stepped thread under control"