Re: [PATCH] make "set debug target" take effect immediately

[Tom Tromey <tromey@redhat.com>]

>>>>> "Yao" == Tom Tromey <tromey@redhat.com> writes:

Tom> What do you think of the appended?

Yao> We need to replace "target_resume" in the comments several lines above
Yao> too,

Tom> Thanks.  I've fixed it locally.

Here is what I am checking in.

Tom

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/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
     }