This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: backtrace/1250: [regression] bad backtrace when function that calls 'abort' at end
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: cagney at redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 2 Aug 2003 01:28:00 -0000
- Subject: Re: backtrace/1250: [regression] bad backtrace when function that calls 'abort' at end
- Reply-to: Daniel Jacobowitz <drow at mvista dot com>
The following reply was made to PR backtrace/1250; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@mvista.com>
To: mec@shout.net, cagney@redhat.com, gdb-prs@sources.redhat.com,
gdb-gnats@sources.redhat.com
Cc:
Subject: Re: backtrace/1250: [regression] bad backtrace when function that calls 'abort' at end
Date: Fri, 1 Aug 2003 21:21:56 -0400
On Sun, Jul 27, 2003 at 06:09:28PM -0000, mec@shout.net wrote:
> Synopsis: [regression] bad backtrace when function that calls 'abort' at end
>
> State-Changed-From-To: closed->open
> State-Changed-By: chastain
> State-Changed-When: Sun Jul 27 18:09:28 2003
> State-Changed-Why:
> It's fixed with -gdwarf-2, but it's still broken for -gstabs+.
>
> Try the "stabs.exe" file in the attachment:
>
> gdb stabs.exe
> break abort
> run
> backtrace
>
> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1250
See
http://sources.redhat.com/ml/gdb/2003-08/msg00030.html
This is related to frame_unwind_address_in_block.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer