From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: [commit] cleanup annota*.exp ``cleanup core file'' messages
Date: Mon, 12 Jul 2004 21:43:00 -0000 [thread overview]
Message-ID: <40F305DE.8090805@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 172 bytes --]
Hello,
Dependant on your system, and how other tests went, the annota[13].exp
tests output different ``cleanup core file'' messages. This fixes that.
committed,
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2323 bytes --]
2004-07-12 Andrew Cagney <cagney@gnu.org>
* gdb.base/annota1.exp: Cleanup corefile test name.
* gdb.base/annota3.exp: Ditto.
Index: gdb.base/annota1.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/annota1.exp,v
retrieving revision 1.13
diff -p -u -r1.13 annota1.exp
--- gdb.base/annota1.exp 6 Nov 2003 20:50:47 -0000 1.13
+++ gdb.base/annota1.exp 12 Jul 2004 21:37:52 -0000
@@ -459,20 +459,20 @@ gdb_expect {
}
-# Check for production of a core file
-# and remove it!
+# Check for production of a core file and remove it!
set exec_output [remote_exec build "ls core"]
+set test "cleanup core file"
if [ regexp "core not found" $exec_output] {
- pass "No core dumped"
+ pass "$test (not dumped)"
} else {
- if [ regexp "No such file or directory" $exec_output] {
- pass "No core dumped"
- } else {
- remote_exec build "rm -f core"
- pass "Core dumped and removed"
- }
+ if [ regexp "No such file or directory" $exec_output] {
+ pass "$test (not dumped)"
+ } else {
+ remote_exec build "rm -f core"
+ pass "$test (removed)"
+ }
}
# restore the original prompt for the rest of the testsuite
Index: gdb.base/annota3.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/annota3.exp,v
retrieving revision 1.2
diff -p -u -r1.2 annota3.exp
--- gdb.base/annota3.exp 17 Aug 2003 16:50:59 -0000 1.2
+++ gdb.base/annota3.exp 12 Jul 2004 21:37:52 -0000
@@ -387,20 +387,20 @@ gdb_expect_list "signal sent" "$gdb_prom
}
-# Check for production of a core file
-# and remove it!
+# Check for production of a core file and remove it!
set exec_output [remote_exec build "ls core"]
+set test "cleanup core file"
if [ regexp "core not found" $exec_output] {
- pass "No core dumped"
+ pass "$test (not dumped)"
} else {
- if [ regexp "No such file or directory" $exec_output] {
- pass "No core dumped"
- } else {
- remote_exec build "rm -f core"
- pass "Core dumped and removed"
- }
+ if [ regexp "No such file or directory" $exec_output] {
+ pass "$test (not dumped)"
+ } else {
+ remote_exec build "rm -f core"
+ pass "$test (removed)"
+ }
}
# restore the original prompt for the rest of the testsuite
next reply other threads:[~2004-07-12 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 21:43 Andrew Cagney [this message]
2004-07-12 22:48 Michael Elizabeth Chastain
2004-07-13 18:44 Michael Elizabeth Chastain
2004-07-14 14:53 ` Andrew Cagney
2004-07-14 17:47 Michael Elizabeth Chastain
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=40F305DE.8090805@gnu.org \
--to=cagney@gnu.org \
--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