diff options
| author | Pedro Alves <palves@redhat.com> | 2015-03-05 23:39:46 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2015-03-05 23:40:39 +0000 |
| commit | 9494d2199f5ce0cf2a4cf5628f23ae91d933955d (patch) | |
| tree | 2552ea107f836b6689961946ac9055c662eed3e3 /gdb/testsuite/gdb.base | |
| parent | 68901c4d439ebceecab927932c17ea1504747c02 (diff) | |
| download | gdb-9494d2199f5ce0cf2a4cf5628f23ae91d933955d.zip gdb-9494d2199f5ce0cf2a4cf5628f23ae91d933955d.tar.gz gdb-9494d2199f5ce0cf2a4cf5628f23ae91d933955d.tar.bz2 | |
gdb.base/bp-permanent.exp: Tighten regex
Trying to fix a permanent breakpoints bug, I broke "next" over a
regular breakpoint. "next" would immediately hit the breakpoint the
program was already stopped at. But, the "next over setup" test
failed to notice this and still issued a pass. That's because the
regex matches "testsuite" in:
Breakpoint 2 at 0x400687: file src/gdb/testsuite/gdb.base/bp-permanent.c, line 46.
gdb/testsuite/ChangeLog:
2015-03-05 Pedro Alves <palves@redhat.com>
* gdb.base/bp-permanent.exp: Tighten "next over setup" regex.
Diffstat (limited to 'gdb/testsuite/gdb.base')
| -rw-r--r-- | gdb/testsuite/gdb.base/bp-permanent.exp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.base/bp-permanent.exp b/gdb/testsuite/gdb.base/bp-permanent.exp index d0ed991..81a5293 100644 --- a/gdb/testsuite/gdb.base/bp-permanent.exp +++ b/gdb/testsuite/gdb.base/bp-permanent.exp @@ -96,7 +96,7 @@ proc test {always_inserted sw_watchpoint} { # Run the "setup" function in the inferior. This memcpy's the # breakpoint instruction to a buffer in the inferior. - gdb_test "next" "test.*" "next over setup" + gdb_test "next" "test_basics \\(\\).*" "next over setup" delete_breakpoints |