fix test suite regression
This fixes a test suite regession that Yao noticed. This test checks for some specific "target debug" output that has changed since the test was written. 2014-08-04 Tom Tromey <tromey@redhat.com> * gdb.base/sss-bp-on-user-bp-2.exp: Match "to_resume", not "target_resume".
This commit is contained in:
parent
78a4993b90
commit
00b51ff583
|
@ -1,3 +1,8 @@
|
|||
2014-08-04 Tom Tromey <tromey@redhat.com>
|
||||
|
||||
* gdb.base/sss-bp-on-user-bp-2.exp: Match "to_resume", not
|
||||
"target_resume".
|
||||
|
||||
2014-08-01 Joel Brobecker <brobecker@adacore.com>
|
||||
|
||||
* gdb.base/vla-datatypes.c (vla_factory): Add new variable
|
||||
|
|
|
@ -53,7 +53,7 @@ delete_breakpoints
|
|||
# traffic. Hardware-step targets that can't access memory while the
|
||||
# target is running, either remote or native, are likewise affected.
|
||||
# So we just skip the test if not using software single-stepping. We
|
||||
# detect that by looking for 'target_resume (..., step)' in "debug
|
||||
# detect that by looking for 'to_resume (..., step)' in "debug
|
||||
# target" output.
|
||||
|
||||
# Probe for software single-step breakpoint use.
|
||||
|
@ -62,7 +62,7 @@ gdb_test_no_output "set debug target 1"
|
|||
set hardware_step 0
|
||||
set test "probe target hardware step"
|
||||
gdb_test_multiple "si" $test {
|
||||
-re "target_resume \\(\[^\r\n\]+, step, .*$gdb_prompt $" {
|
||||
-re "to_resume \\(\[^\r\n\]+, step, .*$gdb_prompt $" {
|
||||
set hardware_step 1
|
||||
pass $test
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue