From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30212 invoked by alias); 4 Feb 2003 17:17:01 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 30196 invoked from network); 4 Feb 2003 17:17:00 -0000 Received: from unknown (HELO jackfruit.Stanford.EDU) (171.64.38.136) by 172.16.49.205 with SMTP; 4 Feb 2003 17:17:00 -0000 Received: (from carlton@localhost) by jackfruit.Stanford.EDU (8.11.6/8.11.6) id h14HGwU29445; Tue, 4 Feb 2003 09:16:58 -0800 X-Authentication-Warning: jackfruit.Stanford.EDU: carlton set sender to carlton@math.stanford.edu using -f To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com, Michael Elizabeth Chastain Subject: Re: [patch] KFAIL gdb/1025 References: <20030204144415.GA30443@nevyn.them.org> From: David Carlton Date: Tue, 04 Feb 2003 17:17:00 -0000 In-Reply-To: <20030204144415.GA30443@nevyn.them.org> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-02/txt/msg00118.txt.bz2 On Tue, 4 Feb 2003 09:44:15 -0500, Daniel Jacobowitz 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