aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorTom Tromey <tromey@redhat.com>2014-07-29 13:31:00 -0600
committerTom Tromey <tromey@redhat.com>2014-08-04 08:07:51 -0600
commit00b51ff5835770104952dca3f9addb8f1025a24b (patch)
tree68b73195cbd19f4ddfc4530a883ef7e0e5918c2e /gdb
parent78a4993b90b00289d015305a9eb1948fab9baf91 (diff)
downloadgdb-00b51ff5835770104952dca3f9addb8f1025a24b.zip
gdb-00b51ff5835770104952dca3f9addb8f1025a24b.tar.gz
gdb-00b51ff5835770104952dca3f9addb8f1025a24b.tar.bz2
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".
Diffstat (limited to 'gdb')
-rw-r--r--gdb/testsuite/ChangeLog5
-rw-r--r--gdb/testsuite/gdb.base/sss-bp-on-user-bp-2.exp4
2 files changed, 7 insertions, 2 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index eeeab3e..1ff7249 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -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
diff --git a/gdb/testsuite/gdb.base/sss-bp-on-user-bp-2.exp b/gdb/testsuite/gdb.base/sss-bp-on-user-bp-2.exp
index a196f68..cb95da0 100644
--- a/gdb/testsuite/gdb.base/sss-bp-on-user-bp-2.exp
+++ b/gdb/testsuite/gdb.base/sss-bp-on-user-bp-2.exp
@@ -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
}