From: Corinna Vinschen <gdb-patches@sources.redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] testsuite/gdb.base/bang.exp: Allow trailing text after "Program exited normally"
Date: Mon, 08 Sep 2003 11:42:00 -0000 [thread overview]
Message-ID: <20030908114200.GG1859@cygbert.vinschen.de> (raw)
Hi,
while testing I found that a test for ending the program in
gdb.base/bang.exp failed, even though the target had actually
exited normally. The cause of the FAIL is that bang.exp doesn't
expect anything after the string "Program exited normally.".
On the sh target at least, the output after exiting contains a
bit more text:
Program exited normally.
[Switching to process 0]
Since that trailing output after a normal exit doesn't change
anything with respect to the testresult, I propose to allow
trailing characters:
* testsuite/gdb.base/bang.exp: Allow trailing text after
"Program exited normally." string.
Index: testsuite/gdb.base/bang.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/bang.exp,v
retrieving revision 1.1
diff -u -p -r1.1 bang.exp
--- testsuite/gdb.base/bang.exp 24 Jun 2003 22:04:06 -0000 1.1
+++ testsuite/gdb.base/bang.exp 8 Sep 2003 11:29:38 -0000
@@ -36,6 +36,6 @@ gdb_load ${binfile}
# Verify that we can run the program and that it terminates normally.
gdb_test "run" \
- ".*Program exited normally\." \
+ ".*Program exited normally\..*" \
"run program"
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
next reply other threads:[~2003-09-08 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 11:42 Corinna Vinschen [this message]
2003-09-08 13:27 ` Daniel Jacobowitz
2003-09-08 14:30 ` Corinna Vinschen
2003-09-08 14:52 ` Daniel Jacobowitz
2003-09-08 15:39 ` Corinna Vinschen
2003-09-08 18:52 ` Andrew Cagney
2003-09-08 20:14 ` Daniel Jacobowitz
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=20030908114200.GG1859@cygbert.vinschen.de \
--to=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