From: Fernando Nasser <fnasser@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ac131313@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Remove all setup_xfail's from testsuite/gdb.mi/
Date: Thu, 16 Jan 2003 14:20:00 -0000 [thread overview]
Message-ID: <3E26BF96.2030607@redhat.com> (raw)
In-Reply-To: <200301151744.h0FHi6O27664@duracef.shout.net>
Michael Elizabeth Chastain wrote:
>
> I agree with Fernando that it's okay to tie every XFAIL to a gdb PR
> and turn it into a KFAIL (at least, I think he is saying that).
>
Right.
> Let's take a specific case. gdb.base/constvars.exp has a lot of
> tests such as "const char * foo ; ptype foo". With gcc 2.95.3/stabs+,
> the "ptype" prints "char * foo". This happens because gcc 2.95.3/stabs+
> does not put any const information in the stabs. This is probably never
> going to get fixed in the gcc 2 series.
>
That is a true XFAIL, but it should be conditional to version 2 compilers and
stabs, so that it does not show as XPASS everywhere else.
> Now the real problem comes to light. 'K' and 'X' are really orthogonal.
> 'K' means that we know about the problem, and 'X' means that it is
> a problem in an external tool, and these two things are separate.
> But we made them an either/or, so we have to choose.
>
> I'd rather have this become a KFAIL with reference to a gdb PR. Then
> the gdb PR can say that this incorrect behavior happens, but it's not
> gdb's fault. The gdb PR should refer to a gcc PR or other external PR.
> And then we can't close the gdb PR until gcc revives gcc 2.X development
> or gdb drop supports for gcc 2.X.
>
> We could add another PR state for these kind of PR's, or we could
> just use the 'suspended' state.
>
The Dejagnu community will kill me if I come out with yet another type of
failure ;-) The problem is that the international standard don't even recognize
these extensions we've added (XFAIL and KFAIL), although I think they are really
important and your weekely reports prove that.
>>From the gdb user's point of view, a bug is a bug. A gdb user can do
> the same thing as the test suite and then file a PR: 'gdb fails to
> print 'const' for const types'.
>
Yes, but we have little control over what we call XFAIL cases. But you have a
good point that they deserve some user documentation as much as the KFAILs do.
Please see my reply to Daniel's message.
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2003-01-16 14:20 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 17:44 Michael Elizabeth Chastain
2003-01-15 17:51 ` Daniel Jacobowitz
2003-01-16 14:27 ` Fernando Nasser
2003-01-16 14:30 ` Daniel Jacobowitz
2003-01-16 14:46 ` Fernando Nasser
2003-01-16 14:52 ` Daniel Jacobowitz
2003-01-16 15:46 ` Andrew Cagney
2003-01-16 14:20 ` Fernando Nasser [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 19:32 Michael Elizabeth Chastain
2003-01-17 19:28 Michael Elizabeth Chastain
2003-01-17 19:34 ` Daniel Jacobowitz
2003-01-17 19:00 Michael Elizabeth Chastain
2003-01-17 19:16 ` David Carlton
2003-01-17 19:20 ` David Carlton
2003-01-17 19:30 ` Daniel Jacobowitz
2003-01-17 19:28 ` Andrew Cagney
2003-01-16 20:06 Michael Elizabeth Chastain
2003-01-16 20:12 ` Daniel Jacobowitz
2003-01-17 14:12 ` Fernando Nasser
2003-01-17 16:05 ` Andrew Cagney
2003-01-17 14:26 ` Fernando Nasser
2003-01-16 17:12 Michael Elizabeth Chastain
2003-01-16 17:07 Michael Elizabeth Chastain
2002-10-24 11:41 Andrew Cagney
2002-10-24 12:09 ` Daniel Jacobowitz
2002-10-24 12:29 ` Andrew Cagney
2002-10-24 12:58 ` Daniel Jacobowitz
2002-10-24 14:22 ` Andrew Cagney
2002-10-24 14:26 ` Daniel Jacobowitz
2002-10-24 14:39 ` Michael Snyder
2002-10-24 16:31 ` Andrew Cagney
2002-10-24 16:36 ` Michael Snyder
2002-10-24 14:50 ` Andrew Cagney
2002-10-24 14:58 ` Michael Snyder
2002-10-24 15:31 ` Ben Elliston
2002-10-24 16:44 ` Andrew Cagney
2002-10-24 17:35 ` Michael Snyder
2002-10-24 18:25 ` Andrew Cagney
2002-10-24 14:18 ` Michael Snyder
2002-10-24 14:32 ` Andrew Cagney
2002-10-24 14:39 ` David Carlton
2002-10-24 14:57 ` Andrew Cagney
2002-10-24 15:00 ` Michael Snyder
2002-10-24 15:26 ` David Carlton
2002-10-24 15:36 ` Andrew Cagney
2003-01-15 15:55 ` Andrew Cagney
2003-01-15 17:25 ` Fernando Nasser
2003-01-16 16:53 ` Andrew Cagney
2003-01-16 17:05 ` Daniel Jacobowitz
2003-01-16 19:03 ` Andrew Cagney
2003-01-16 19:55 ` 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=3E26BF96.2030607@redhat.com \
--to=fnasser@redhat.com \
--cc=ac131313@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