From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13091 invoked by alias); 5 Nov 2004 22:11:20 -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 13082 invoked from network); 5 Nov 2004 22:11:19 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 5 Nov 2004 22:11:19 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iA5MBJe2009045 for ; Fri, 5 Nov 2004 17:11:19 -0500 Received: from localhost.redhat.com (to-dhcp51.toronto.redhat.com [172.16.14.151]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iA5MBEr08810; Fri, 5 Nov 2004 17:11:14 -0500 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 8FF7A129D8C; Fri, 5 Nov 2004 17:10:55 -0500 (EST) Message-ID: <418BFA6B.3060103@gnu.org> Date: Fri, 05 Nov 2004 22:11:00 -0000 From: Andrew Cagney User-Agent: Mozilla Thunderbird 0.8 (X11/20041020) MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Mark Kettenis , gdb-patches@sources.redhat.com Subject: Re: [COMMIT] Fix decoding CIE's in DWARF frame info References: <200411051543.iA5Fh1nK020633@juw15.nfra.nl> <418BB19C.7000100@gnu.org> <200411051853.iA5IrpfP014435@elgar.sibelius.xs4all.nl> <418BEEF9.4050507@gnu.org> <20041105212505.GA31737@nevyn.them.org> In-Reply-To: <20041105212505.GA31737@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-11/txt/msg00097.txt.bz2 Daniel Jacobowitz wrote: > On Fri, Nov 05, 2004 at 04:22:01PM -0500, Andrew Cagney wrote: > >>>Anyway, I noticed the problem when writing some code at work. >>>Unfortunately I don't know how to convert it into a test case. >> >>I was thinking regression testing. I'm finding that: >> ./gdb foo >> (gdb) run >>gets a panic on CFI systems - RHEL 3 amd64, FC3 i386 and amd64. >> >>Can we set this patch aside until we know what's going on? We can then >>think about a backport for 6.3.1. > > > It does not show any problems here, on Debian i386 (using FCI). You'll need to be more specific RHEL 3 / FC3 tie things down to specific versions (gcc 3.2.3++ and gcc 3.4.2++ from memory). Andrew