--- Comment #6 from scovich at gmail dot com 2010-05-07 21:20 ---
Aha! The problem is not that gcc fails to emit the proper debug info, it's that
it doesn't always track well which instructions came from which function.
For example, if we compile this toy program:
int volatile global
--- Comment #5 from scovich at gmail dot com 2010-05-07 20:12 ---
Belated follow-up: I just tried to use sparc-sun-solaris2.10-gcc-4.4.0 (built
from sources) and it does not emit the DW_AT_call_* debug attributes which gdb
expects in order to unwind inlined functions.
I have searched b
--- Comment #4 from scovich at gmail dot com 2010-04-23 23:29 ---
> Try the -i option of addr2line.
Ah, very nice. It turns out I was using a 4.0-series gcc, which according to
gdb's docs doesn't output quite enough debug information to reconstruct inlined
stack traces; 4.1 and later do
--- Comment #3 from wilson at codesourcery dot com 2010-04-23 22:40 ---
Subject: Re: New: Emit debug info allowing inlined functions
to show in stack traces
On 04/21/2010 02:26 AM, scovich at gmail dot com wrote:
> It would be very nice if gcc emitted debug information that allowed p
--- Comment #2 from jakub at gcc dot gnu dot org 2010-04-21 10:03 ---
GCC already emits that (and emits that for quite some time already).
--
jakub at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #1 from scovich at gmail dot com 2010-04-21 09:29 ---
(In reply to comment #0)
One more way debugging would improve: it would become possible to set
breakpoints in inlined functions
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43828
