From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30925 invoked by alias); 4 Aug 2008 16:25:21 -0000 Received: (qmail 30900 invoked by uid 22791); 4 Aug 2008 16:25:20 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 04 Aug 2008 16:24:40 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m74GObIB016745; Mon, 4 Aug 2008 12:24:38 -0400 Received: from zebedee.charmers (vpn-14-48.rdu.redhat.com [10.11.14.48]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m74GONvF004492; Mon, 4 Aug 2008 12:24:24 -0400 Message-ID: <48972D36.4010005@redhat.com> Date: Mon, 04 Aug 2008 16:25:00 -0000 From: Andrew Haley User-Agent: Thunderbird 2.0.0.16 (X11/20080707) MIME-Version: 1.0 To: Barry Andrews CC: gcc-help@gcc.gnu.org Subject: Re: Mixing exception handling libraries with non exception handling References: <489714C9.6010109@gmail.com> <48971938.40203@redhat.com> <48971DE4.90804@gmail.com> <48971F5D.4090508@redhat.com> <48972282.2060208@gmail.com> <489725F8.5040801@redhat.com> <489728DE.50403@gmail.com> In-Reply-To: <489728DE.50403@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2008-08/txt/msg00035.txt.bz2 Barry Andrews wrote: > Andrew Haley wrote: >> >> Yes, it is always true AFAIAA. The unwinder reads the data lazily, >> so unless it actually finds a stack frame belonging to code that has >> no unwinder data, that should have no effect. The instant the unwinder >> sees a frame that it can't unwind, it will abort: there is nothing >> else it can do. >> >> Note this: the abort is from within the unwinder, WHILE IT IS >> TRYING TO UNWIND A ROUTINE WITH NO UNWINDER DATA. So, you have >> to try to find out why that is happening. >> >> gdb is your friend here. >> > And that's why it aborts for me. There is no unwinder data at all. I'll > keep digging, but there are lots of internals here to debug. OK, so you have to look at a gdb backtrace to see which routine with no unwinder data is being unwound. >>> Is there no work around for this? It seems so very strange to me. >>> >> >> Compile with -fexceptions. >> > Yeah, I have that. Doesn't help. Did it work for you? Yes, always. Andrew.