Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ac131313@redhat.com, drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Remove all setup_xfail's from testsuite/gdb.mi/
Date: Fri, 17 Jan 2003 14:26:00 -0000	[thread overview]
Message-ID: <3E28129D.9050907@redhat.com> (raw)
In-Reply-To: <200301162006.h0GK65K18945@duracef.shout.net>



Michael Elizabeth Chastain wrote:> My two cents ...
> 
> Daniel J suggests that we keep making improvements:
>   > XFAIL->KFAIL
>   > random XFAIL->analyzed XFAIL
>   > XFAIL->PASS
> 
> The problem is that, in the source code, "setup_xfail" looks the same
> for both our crap legacy XFAIL's and the nice new analyzed xfail's.
> 
> Perhaps a little mechanism like "gdb_mark_external_fail" would help.
> Then "grep xfail" would find only the shrinking pool of old stuff.
> 

You are right, we need some way to distinguish what have been verified and what 
has not yet been.

But if we do what Andrew proposes and get rid of all old PR and HP bug number 
markings we can make the distinction visually.  setup_xfail lines without a bug 
number have not yet been verified.  There aren't that many that would make it so 
hard, and the poorly marked ones related to stabs or old compilers do show up in 
your reports very clearly (just diff with a dwarf2 on a new compiler results). 
And as the reports point out, there are only 71 that are not that case.

Just one note: there are cases where the XFAIL is produced by a 'xfail' command 
inside a '-re' clause.


One variation of your idea:

The case for debugger format and compiler version is so common that I would feel 
tempted to have a special function for that.  Something like

gdb_compiler_related_xfail <format> <version spec> <target>+ <bug id (external)>

<format> could be "stabs", "dwarf2", "any"

<version spec>  not sure.  A list? An expression? Suggestions?

<target>+ one or more target specs, as currently (we may even make it optional 
meaning *-*-*)

<bug id>  a bug id, which, of course, will be categorized as "external"



> 
>>This I definitely like.  "Cantfix"?
> 
> 
> I propose "external".
> 
> I find "cantfix" to be a bit arrogant and a bit negative.  And it doesn't
> distinguish between "I can't fix this because I don't have the resources"
> versus "I can't fix this because I can show you that binutils is feeding
> gdb incorrect / incomplete information".
> 

Agreed.



-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  parent reply	other threads:[~2003-01-17 14:26 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [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 17:12 Michael Elizabeth Chastain
2003-01-16 17:07 Michael Elizabeth Chastain
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
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=3E28129D.9050907@redhat.com \
    --to=fnasser@redhat.com \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.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