From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] kfail gdb.c++/annota2.exp annotate-quit
Date: Fri, 20 Dec 2002 10:09:00 -0000 [thread overview]
Message-ID: <20021220171322.GA2610@nevyn.them.org> (raw)
In-Reply-To: <3E034D80.7060904@redhat.com>
On Fri, Dec 20, 2002 at 05:04:00PM +0000, Andrew Cagney wrote:
> >On Wed, Dec 18, 2002 at 11:47:49PM -0600, Michael Elizabeth Chastain wrote:
> >
> >>My testbed gives me 34 KFAIL's on 34 configurations, just fine.
> >>This is native i686-pc-linux-gnu, gcc v2 and v3, dwarf-2 and stabs+.
> >>
> >>I use stock FSF dejagnu 1.4.3. I also built dejagnu from the
> >>sourcware cvs "dejagnu" module and did a test run with that.
> >>That works fine too.
> >>
> >>I have appended a gdb.sum file for anyone who is curious.
> >>The KFAIL line looks like this:
> >>
> >> KFAIL: gdb.c++/annota2.exp: annotate-quit (PRMS: c++/544)
> >>
> >>We can't do anything about the "PRMS:" part, that comes from dejagnu.
> >>
> >>I have an objection to the name "c++/544". It is way too easy for
> >>this name to get quoted out of context (the context being that it is
> >>a gdb bug in the gdb database). I think this will cause confusion.
> >>I would like to see "gdb/544" here.
> >>
> >>Sure, right *now* while we are discussing the issue, everyone knows
> >>that "c++/544" means a gdb bug in the gdb PR database. Wait six weeks
> >>and then quote some people a gdb.sum report that says "c++/482" in it
> >>and see if anyone jumps to the incorrect conclusion that c++/482 means
> >>a bug in the C++ compiler.
> >
> >
> >I want the C++ part in there. How about "PRMS: [gdb] c++/544"?
>
> Just gdb/NNN is better - identify the bug database and not the category.
> Otherwize everytime someone changes a bug category, they have to go
> and update the corresponding testsuite kfail entry (Ulgh!). Also, as
> michael-c points out, you can't determine if a c++/NNN is gdb or gcc (I
> think it is reasonable for kfails's to refer to the gcc bug database).
>
> (I think this has come up before)
It has, shame on me. gdb/544 will be fine then. It's still
GNATS-centric but it'll be pretty clear even after we move (hopefully)
to Bugzilla.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-20 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2002-12-20 10:50 ` David Carlton
-- strict thread matches above, loose matches on Subject: below --
2002-12-18 20:57 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=20021220171322.GA2610@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.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