This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[RFA] Fix bug in templates.exp
- To: gdb-patches at sources dot redhat dot com
- Subject: [RFA] Fix bug in templates.exp
- From: Michael Snyder <msnyder at cygnus dot com>
- Date: Wed, 7 Nov 2001 17:14:38 -0800
- Cc: jimb at redhat dot com, mec at shout dot net
This one is generic (ie. not related to V2/V3 differences).
If the breakpoint command results in an overload menu,
but the output does not match what the test expects,
we still need to issue the cancel command or else the
next test is guaranteed to fail.
2001-11-07 Michael Snyder <msnyder@redhat.com>
* gdb.c++/templates.exp (test_template_breakpoints):
If we get an overload menu, but it does not match what
we expect, we still need to issue the "cancel" command.
Index: gdb.c++/templates.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.c++/templates.exp,v
retrieving revision 1.5
diff -c -3 -p -r1.5 templates.exp
*** templates.exp 2001/04/24 17:47:42 1.5
--- templates.exp 2001/11/08 01:11:56
*************** proc test_template_breakpoints {} {
*** 114,120 ****
"canceled" \
"constructor breakpoint"
}
! -re ".*\n> $" { fail "constructor breakpoint" }
-re ".*$gdb_prompt $" { fail "constructor breakpoint" }
default { fail "constructor breakpoint (timeout)" }
}
--- 114,124 ----
"canceled" \
"constructor breakpoint"
}
! -re ".*\n> $" {
! gdb_test "0" \
! "nonsense intended to insure that this test fails" \
! "constructor breakpoint (bad menu choices)"
! }
-re ".*$gdb_prompt $" { fail "constructor breakpoint" }
default { fail "constructor breakpoint (timeout)" }
}