From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30674 invoked by alias); 29 Jul 2004 21:24:53 -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 30652 invoked from network); 29 Jul 2004 21:24:52 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sourceware.org with SMTP; 29 Jul 2004 21:24:52 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 6051047D91; Thu, 29 Jul 2004 14:24:51 -0700 (PDT) Date: Thu, 29 Jul 2004 21:24:00 -0000 From: Joel Brobecker To: Andrew Cagney Cc: gdb-patches@sources.redhat.com Subject: Re: GDB 6.2 branch frozen Message-ID: <20040729212451.GJ1167@gnat.com> References: <41080494.1060306@gnu.org> <20040728235303.GD1167@gnat.com> <41094AA3.9000900@gnu.org> <20040729204735.GI1167@gnat.com> <4109687F.7020708@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4109687F.7020708@gnu.org> User-Agent: Mutt/1.4i X-SW-Source: 2004-07/txt/msg00459.txt.bz2 > Once the BFD patch is applied, what's next to fail? I think the next biggie is the unwinder. But there is also the problem with floats that cause GDB to SEGV. The last one is on my plate, but the patch could still be applied as is. It might not be perfect (we need to check) but at least it prevents the crash. References: http://sources.redhat.com/ml/gdb-patches/2004-07/msg00288.html http://sources.redhat.com/ml/gdb-patches/2004-07/msg00319.html http://sources.redhat.com/ml/gdb-patches/2004-07/msg00310.html -- Joel