From: Jim Blandy <jimb@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: don't xfail ptype test
Date: Fri, 10 May 2002 11:33:00 -0000 [thread overview]
Message-ID: <npr8kj4zuy.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <200205101655.g4AGtIn01593@duracef.shout.net>
Michael Elizabeth Chastain <mec@shout.net> writes:
> This patch is returned for more work.
>
> Hmmm. I agree that this is a bug:
>
> (gdb) ptype &*"foo"
> type = char [4]
>
> I get that behavior in all of my configurations.
>
> The problem is simply converting XFAIL -> FAIL. That's correct, but it
> doesn't leave a good enough trail for people doing regression analysis.
>
> Could you please file a bug report and then add a comment to the
> test script with the bug ID number in it:
>
> # setup_kfail "gdb/1234"
>
> The bug report can say that this bug is also present in 5.2.
>
> I am willing to file the bug report this evening if you want me to
> do that part.
>
> Michael C
Okay, how's the below? What's setup_kfail? Where can I find a
description of it?
2002-05-10 Jim Blandy <jimb@redhat.com>
* gdb.base/printcmds.exp: Don't xfail the ptype command. This is
a bug.
Index: gdb/testsuite/gdb.base/printcmds.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/printcmds.exp,v
retrieving revision 1.7
diff -c -r1.7 printcmds.exp
*** gdb/testsuite/gdb.base/printcmds.exp 4 May 2002 15:18:21 -0000 1.7
--- gdb/testsuite/gdb.base/printcmds.exp 10 May 2002 18:05:04 -0000
***************
*** 626,633 ****
gdb_test "ptype \"foo\"" " = char \\\[4\\\]"
gdb_test "p *\"foo\"" " = 102 'f'"
gdb_test "ptype *\"foo\"" " = char"
gdb_test "p &*\"foo\"" " = \"foo\""
- setup_xfail "*-*-*"
gdb_test "ptype &*\"foo\"" "type = char \\*"
gdb_test "p (char *)\"foo\"" " = \"foo\""
}
--- 626,633 ----
gdb_test "ptype \"foo\"" " = char \\\[4\\\]"
gdb_test "p *\"foo\"" " = 102 'f'"
gdb_test "ptype *\"foo\"" " = char"
+ # setup_kfail "gdb/538"
gdb_test "p &*\"foo\"" " = \"foo\""
gdb_test "ptype &*\"foo\"" "type = char \\*"
gdb_test "p (char *)\"foo\"" " = \"foo\""
}
next prev parent reply other threads:[~2002-05-10 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 9:55 Michael Elizabeth Chastain
2002-05-10 11:33 ` Jim Blandy [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 18:47 Michael Elizabeth Chastain
2002-05-10 12:13 Michael Elizabeth Chastain
2002-05-10 13:25 ` Jim Blandy
2002-05-10 9:17 Jim Blandy
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=npr8kj4zuy.fsf@zwingli.cygnus.com \
--to=jimb@redhat.com \
--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