From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] testsuite/gdb.base/commands.exp: Don't expect "Program exited normally" string
Date: Fri, 13 Sep 2002 07:49:00 -0000 [thread overview]
Message-ID: <20020913164944.F1574@cygbert.vinschen.de> (raw)
Hi,
the command.exp test expects the string "Program exited normally" when
testing commands execution on breakpoints. This might fail on some
remote targets and simulators which never reaches a normal exit but
stop execution at some defined trap in _exit() or friend.
For that reason I'd propose to drop the above expectation from the test.
Corinna
* gdb.base/commands.exp: Don't expect a "Program exited normally"
string after running the commands execution on breakpoint tests.
Index: gdb.base/commands.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/commands.exp,v
retrieving revision 1.11
diff -u -p -r1.11 commands.exp
--- gdb.base/commands.exp 27 Aug 2002 01:09:09 -0000 1.11
+++ gdb.base/commands.exp 13 Sep 2002 14:45:28 -0000
@@ -490,7 +490,7 @@ proc bp_deleted_in_command_test {} {
gdb_run_cmd
gdb_expect {
- -re ".*factorial command-list executed.*1.*Program exited normally.*$gdb_prompt $" {
+ -re ".*factorial command-list executed.*1.*$gdb_prompt $" {
pass "run factorial until breakpoint"
}
-re ".*$gdb_prompt $" {
@@ -547,7 +547,7 @@ proc temporary_breakpoint_commands {} {
gdb_run_cmd
gdb_expect {
- -re ".*factorial tbreak commands executed.*1.*Program exited normally.*" {
+ -re ".*factorial tbreak commands executed.*1.*$gdb_prompt $" {
pass "run factorial until temporary breakpoint"
}
timeout { fail "(timeout) run factorial until temporary breakpoint" }
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:vinschen@redhat.com
next reply other threads:[~2002-09-13 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 7:49 Corinna Vinschen [this message]
2002-09-13 12:11 ` Fernando Nasser
2002-09-14 2:32 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020913164944.F1574@cygbert.vinschen.de \
--to=vinschen@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox