This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/1829: Inline function display and single-stepping
- From: smurf at smurf dot noris dot de
- To: gdb-gnats at sources dot redhat dot com
- Date: 14 Dec 2004 13:48:53 -0000
- Subject: gdb/1829: Inline function display and single-stepping
- Reply-to: smurf at smurf dot noris dot de
>Number: 1829
>Category: gdb
>Synopsis: Inline function display and single-stepping
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Tue Dec 14 13:58:02 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: smurf@smurf.noris.de
>Release: GNU gdb 6.3-debian
>Organization:
>Environment:
Linux, gcc 3.4
>Description:
It currently is basically impossible to step (with "n" )through C and (especially) C++ code which uses inline calls. The inlined code is shown as being inserted into the code which calls it.
That causes "n" to step from one inline function to the next. It is impossible to figure out which 'real' 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.
>How-To-Repeat:
Compile any heavily-inlined code and try to figure out where you are after having pressed "n" a few times.
>Fix:
The gcc folks say they already to their debug information correctly, so that it should be possible to show the code which contains the inlined function call.
>Release-Note:
>Audit-Trail:
>Unformatted: