From: David Carlton <carlton@kealia.com>
To: gdb-patches@sources.redhat.com
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Subject: [commit] change testsuite reference from PR 826 to 1588
Date: Wed, 17 Mar 2004 20:13:00 -0000 [thread overview]
Message-ID: <yf2r7vrxmen.fsf@hawaii.kealia.com> (raw)
Message-ID: <20040317201300.Jim87spGneZUO83FdxC6NY37F5lFqfP1TMlEtxKVMeE@z> (raw)
As discussed in another e-mail thread, I've filed PR gdb/1588 to more
closely match a particular failure in classes.exp; this updates
classes.exp accordingly.
David Carlton
carlton@kealia.com
2004-03-17 David Carlton <carlton@kealia.com>
* gdb.cp/classes.exp (test_enums): Refer to PR c++/1588 instead of
PR c++/826.
Index: classes.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.cp/classes.exp,v
retrieving revision 1.9
diff -u -p -r1.9 classes.exp
--- classes.exp 9 Mar 2004 17:34:39 -0000 1.9
+++ classes.exp 17 Mar 2004 20:10:24 -0000
@@ -703,7 +703,7 @@ proc test_enums {} {
}
# I'll do this test two different ways, because of a parser bug.
- # See PR gdb/826.
+ # See PR gdb/1588.
gdb_test_multiple "print (ClassWithEnum::PrivEnum) 42" "print (ClassWithEnum::PrivEnum) 42" {
-re "\\$\[0-9\]+ = yellow$nl$gdb_prompt $" {
@@ -712,7 +712,7 @@ proc test_enums {} {
-re "A (parse|syntax) error in expression, near `42'.$nl$gdb_prompt $" {
# "parse error" is bison 1.35.
# "syntax error" is bison 1.875.
- kfail "gdb/826" "print (ClassWithEnum::PrivEnum) 42"
+ kfail "gdb/1588" "print (ClassWithEnum::PrivEnum) 42"
}
}
next reply other threads:[~2004-03-17 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 David Carlton [this message]
2004-03-17 20:13 ` 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=yf2r7vrxmen.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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