From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28543 invoked by alias); 7 Aug 2004 18:06:56 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 28528 invoked from network); 7 Aug 2004 18:06:55 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 7 Aug 2004 18:06:55 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i77I6se3029240 for ; Sat, 7 Aug 2004 14:06:55 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i77I6pa18987; Sat, 7 Aug 2004 14:06:51 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 1E3652B9D; Sat, 7 Aug 2004 14:06:45 -0400 (EDT) Message-ID: <41151A34.1000704@gnu.org> Date: Sat, 07 Aug 2004 18:06:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040801 MIME-Version: 1.0 To: Joel Brobecker Cc: gdb@sources.redhat.com Subject: Re: GDB 6.2.1? References: <41128FD4.5020702@gnu.org> <20040805204835.GI1192@gnat.com> <41139F3F.7040508@gnu.org> <20040806161616.GO1192@gnat.com> In-Reply-To: <20040806161616.GO1192@gnat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00111.txt.bz2 >>>>> >>What's left for this re-spin? >>>> >>>>>> >>>- ``absolute source path'' patch >>>>>> >>>- i386 patch >>>>>> >>>- ? >> >>> >>> The MIPS crasher bug is in though. That's the critical one. > > > Actually, no, the crasher bug is still not fixed (it's the one > dealing with the size of long doubles). The patch that we checked in > was fixing "break main". ``break main'' was, for me the crasher bug :-) The criteria explicitly mention ``does it fix "break main; run"'' which it did :-) As for the FP crash, thanks to your bug analysis there's something to stop it in the branch and a mainline fix is well in hand. >>> I don't even remember what that one is. Ah, yes, the backtrace fix, >>> leave that for 6.3. > > > It fixes the backtrace problem, but the problem it fixes also influences > next/step. I still think we're better off shooting for a decent clean-up by 6.3 (in a few months). I'll commit the ``absolute source path'' patch then 6.2.1 is good to go (well depending on how Eli and Mark resolve the i386 change). Andrew