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".

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index eeeab3e89ab0d07dbd465f702f9dce36659f901e..1ff72492b4c7e88d7ec3e044b5bed1c27c505c14 100644 (file)
--- 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 a196f68ee5ce23b0c445c136c6cd5b1c595de190..cb95da03709025feed3a23de615bc0e4c4b08847 100644 (file)
--- 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
     }