It currently is basically impossible to "n" through C and (especially) C++ code
which uses inline code. The inlined code is, conceptually, inserted into the
code which calls it.
That causes next-source instructions in gdb and other debuggers to step from one
inline function to the next. It is impossible to figure out which source line
you're actually looking at.
Likewise, the toplevel frame points to some inline code instead of the function
in which the crash occurred.
I'd like an option to de-inline these code snippets, but only from the
debugger's point of view. Bonus points for making this optional, i.e. switching
between condensed and expanded views, in the debugger at runtime.
--
Summary: Debugging inlined code is *bad*
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: debug
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: smurf at smurf dot noris dot de
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18979
