From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26705 invoked by alias); 22 Jul 2004 04:04:08 -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 26697 invoked from network); 22 Jul 2004 04:04:07 -0000 Received: from unknown (HELO aragorn.inter.net.il) (192.114.186.23) by sourceware.org with SMTP; 22 Jul 2004 04:04:07 -0000 Received: from zaretski (pns03-206-64.inter.net.il [80.230.206.64]) by aragorn.inter.net.il (MOS 3.4.6-GR) with ESMTP id DWH04633; Thu, 22 Jul 2004 07:04:02 +0300 (IDT) Date: Thu, 22 Jul 2004 07:13:00 -0000 From: "Eli Zaretskii" To: Andrew Cagney Message-Id: <6654-Thu22Jul2004070248+0300-eliz@gnu.org> CC: kettenis@chello.nl, gdb@sources.redhat.com In-reply-to: <40FEE8AE.7080300@gnu.org> (message from Andrew Cagney on Wed, 21 Jul 2004 18:05:34 -0400) Subject: Re: [6.2] PROBLEMS file Reply-to: Eli Zaretskii References: <40FB3F1F.3040900@gnu.org> <1659-Mon19Jul2004215127+0300-eliz@gnu.org> <200407212059.i6LKxgQ9019045@copland.kettenis.dyndns.org> <40FEE8AE.7080300@gnu.org> X-SW-Source: 2004-07/txt/msg00277.txt.bz2 > Date: Wed, 21 Jul 2004 18:05:34 -0400 > From: Andrew Cagney > > > So IMHO there is no regression here. PR 1505 should be closed. If > > the length of the backtraces is a problem, we should probably set a > > sensible backtrace limit. > > Try and convince a user of that :-) This is, right or wrong, a > situtation where we're the ones that get to push for a solution. I tend to agree. > To that end, two ideas: > > - add a GNU extension to dwarf2 that identifies the frame as outer-most > > - have the CFI unwinds back to the exact same identical frame (causing > GDB to throw up its hands) This wouldn't help the DJGPP port of Emacs: it is compiled with "-gcoff" (because no one has written code to support unexec with DWARF2 debug info embedded in a COFF binary). It would be much more helpful if someone could documente the inner workings of the frame-unwinding code, including all its different strategies, in gdbint.texinfo. Perhaps then I could debug the problem and at least understand what is causing it; I'm not at all sure it's the function prologue/epilogue issue. TIA