From: Tom Tromey Date: Tue, 29 Jul 2014 19:31:00 +0000 (-0600) Subject: fix test suite regression X-Git-Tag: upstream/2.25~703 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=00b51ff5835770104952dca3f9addb8f1025a24b;p=platform%2Fupstream%2Flinaro-binutils.git 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 * 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 eeeab3e..1ff7249 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2014-08-04 Tom Tromey + + * gdb.base/sss-bp-on-user-bp-2.exp: Match "to_resume", not + "target_resume". + 2014-08-01 Joel Brobecker * 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 }