From: David Carlton <carlton@math.stanford.edu>
To: gdb-patches@sources.redhat.com
Cc: Michael Elizabeth Chastain <mec@shout.net>
Subject: [patch] kfail gdb.c++/annota2.exp annotate-quit
Date: Wed, 18 Dec 2002 20:57:00 -0000 [thread overview]
Message-ID: <ro1hedbkktc.fsf@jackfruit.Stanford.EDU> (raw)
This patch KFAIL's the test 'annotate-quit' in gdb.c++/annota2.exp,
corresponding to PR c++/544. If nobody objects, I'll commit it this
Friday; since it's the first KFAIL in the test suite, though, I wanted
to give people a couple of days to object and/or update their copies
of dejagnu.
Following a suggestion of Michael Chastain, I'm KFAILing only the
explicit regexp that I'm seeing as a failure. Note that, in this
file, gdb_prompt is set to an unusual value, and that unusual value is
in fact the exact output that I'm seeing.
David Carlton
carlton@math.stanford.edu
2002-12-18 David Carlton <carlton@math.stanford.edu>
* gdb.c++/annota2.exp: KFAIL annotate-quit.
Index: annota2.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.c++/annota2.exp,v
retrieving revision 1.6
diff -u -p -r1.6 annota2.exp
--- annota2.exp 13 May 2002 19:18:52 -0000 1.6
+++ annota2.exp 18 Dec 2002 22:17:31 -0000
@@ -214,6 +214,7 @@ send_gdb "\003"
gdb_expect {
-re "\r\n\032\032error-begin\r\nQuit\r\n\r\n\032\032quit\r\n$gdb_prompt$" \
{ pass "annotate-quit" }
+ -re "$gdb_prompt$" { kfail "c++/544" "annotate-quit" }
-re ".*$gdb_prompt$" { fail "annotate-quit" }
timeout { fail "annotate-quit (timeout)" }
}
next reply other threads:[~2002-12-18 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 20:57 David Carlton [this message]
2002-12-19 7:42 Michael Elizabeth Chastain
2002-12-19 11:01 ` David Carlton
2002-12-19 13:48 ` Daniel Jacobowitz
2002-12-20 9:12 ` Andrew Cagney
2002-12-20 10:09 ` Daniel Jacobowitz
2002-12-20 10:50 ` David Carlton
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=ro1hedbkktc.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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