This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/1250 [regression] bad backtrace when function that calls 'abort' at end
- From: Michael Elizabeth Chastain <mec at shout dot net>
- To: cagney at redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 8 Aug 2003 22:08:00 -0000
- Subject: Re: gdb/1250 [regression] bad backtrace when function that calls 'abort' at end
- Reply-to: Michael Elizabeth Chastain <mec at shout dot net>
The following reply was made to PR backtrace/1250; it has been noted by GNATS.
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-gnats@sources.redhat.com
Cc:
Subject: Re: gdb/1250 [regression] bad backtrace when function that calls 'abort' at end
Date: Fri, 8 Aug 2003 17:59:21 -0400
This works now if the calling function is compiled with -gdwarf-2
or with -gstabs+. Tested with both gdb HEAD and gdb gdb_6_0-branch.
It still breaks if the calling function is compiled with no "-g" flag.
This breaks a long tradition of gdb, which is that gdb can backtrace
through code with no debugging symbols, such as library code.
Michael C