Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com,
	Michael Elizabeth Chastain <mec@shout.net>
Subject: Re: [patch] KFAIL gdb/1025
Date: Tue, 04 Feb 2003 17:17:00 -0000	[thread overview]
Message-ID: <ro13cn455km.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20030204144415.GA30443@nevyn.them.org>

On Tue, 4 Feb 2003 09:44:15 -0500, Daniel Jacobowitz <drow@mvista.com> said:

> I'm really not comfortable with this use of KFAIL.  My hope was that
> we would analyze particular failures before KFAILing them off to
> oblivion.  I spent time fixing these exact six failures a bit under
> a month ago; if it isn't working for your setup I want more
> information.

This I disagree with.  Next time, I'll wait a day before KFAILing it,
if you like.  But, from my point of view, what I have done is the
exact opposite of sending them off to oblivion: before I KFAILed them,
the bug was only visible in my test suite and in some of Michael's
test runs, whereas now it's in the much more visible location of an
open bug in the bug database.

If I uncover a new bug, that's one thing: I haven't rushed to file a
bug report+KFAIL for the overloading bug that I turned up last Friday,
because I'm happy to wait for Daniel to look at that patch.  But this
is a failure that I've seen in the test suite since I started working
on GDB and that also shows up on Michael's tables (to some extent).

If, of course, it is a bug.  To answer questions that have been raised
elsewhere:

* I'm using the binutils that comes with Red Hat 7.3; rpm -q reports
  it as binutils-2.11.93.0.2-11.  So it's old.  I'll upgrade that and
  see what happens.  (And then do what to the test?  Turn it from
  KFAIL into XFAIL, I suppose?)

* I gave the wrong GDB version: I was using CVS GDB from yesterday.  I
  saw the FAILs using 'make check' on yesterday's CVS, but then I
  investigated it using whatever GDB happened to be in /usr/local/bin
  (which, if you're curious, is the current dictionary branch GDB, and
  I haven't sync'd with mainline since whatever old date I listed).  I
  try to remember to use CVS GDB when investigating bugs, so I get the
  date entered right, but sometimes I forget.

And I have some other questions/comments:

* If it's all due to binutils, why do Michael's tables still show some
  non-PASS results with GCC 2.95.3/DWARF-2?

* It's not the same as PR 872.  That's about overload resolution; this
  bug doesn't seem to be related to overload resolution.

Anyways, I'll upgrade my binutils when I have some free time (probably
this afternoon) and see how that affects matters.

David Carlton
carlton@math.stanford.edu


  reply	other threads:[~2003-02-04 17:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04  1:18 David Carlton
2003-02-04 14:44 ` Daniel Jacobowitz
2003-02-04 17:17   ` David Carlton [this message]
2003-02-04 17:22     ` Daniel Jacobowitz
2003-02-04 22:28     ` David Carlton
2003-02-06 20:59       ` David Carlton
2003-02-04 15:32 Michael Elizabeth Chastain
2003-02-04 18:33 Michael Elizabeth Chastain
2003-02-04 20:07 Michael Elizabeth Chastain
2003-02-05  6:04 Michael Elizabeth Chastain
2003-02-07 16:16 Michael Elizabeth Chastain
2003-02-07 17:04 ` David Carlton
2003-02-07 17:08 Michael Elizabeth Chastain
2003-02-07 17:13 ` David Carlton
2003-02-07 17:40 Michael Elizabeth Chastain
2003-02-07 17:46 ` 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=ro13cn455km.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --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