From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15783 invoked by alias); 6 Aug 2004 16:16:21 -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 15766 invoked from network); 6 Aug 2004 16:16:17 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sourceware.org with SMTP; 6 Aug 2004 16:16:17 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id E179147D91; Fri, 6 Aug 2004 09:16:16 -0700 (PDT) Date: Fri, 06 Aug 2004 16:16:00 -0000 From: Joel Brobecker To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: GDB 6.2.1? Message-ID: <20040806161616.GO1192@gnat.com> References: <41128FD4.5020702@gnu.org> <20040805204835.GI1192@gnat.com> <41139F3F.7040508@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41139F3F.7040508@gnu.org> User-Agent: Mutt/1.4i X-SW-Source: 2004-08/txt/msg00107.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". > >The first patch was under heavy discussion (about setting the right > >floatformat). I am not where we're headed for this one as I don't have > >the time to work on adding support for IRIX 128bit floats in GDB. > > I think it ended with a compromise of a 128-bit IRIX MIPS floatformat. > I'd also like to know the original details on the crash. OK, so I'll try to work on that asap and send a patch. I'll resend the details of the crash. > >The other one needs to be reworked because Andrew wanted to get some > >reorg done before we looked into this. It's on my plate. > > 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. > >What should we do? Push a bit on the resolution of the above 2 patches? > >Or simply pull them in the branch as is, without having checked > >something in head first (this is unorthodox)? > > (We've all learnt the hard way to not do this). I agree. It's just I wasn't sure about what you meant in your message. -- Joel