This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
tui/2545: Feature request: allow users to specify sets of functions which shouldn't be "stepped into"
- From: f18m_cpp217828 at yahoo dot it
- To: gdb-gnats at sources dot redhat dot com
- Date: 30 Oct 2008 09:56:52 -0000
- Subject: tui/2545: Feature request: allow users to specify sets of functions which shouldn't be "stepped into"
- Reply-to: f18m_cpp217828 at yahoo dot it
>Number: 2545
>Category: tui
>Synopsis: Feature request: allow users to specify sets of functions which shouldn't be "stepped into"
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Thu Oct 30 09:58:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Francesco Montorsi
>Release: unknown-1.0
>Organization:
>Environment:
linux
>Description:
In many cases when debugging step-by-step a program (in my case C++), you have to deal with lines like:
call_of_interest( new blah( "a", 1 ), my_vector.begin(), my_vector.end() );
if you want to step into call_of_interest(), you'll have to first step into all the function calls that produce its arguments. This is very annoying.
Microsoft Visual Studio solved the problem introducing a user-customizable list of functions which should _NOT_ be entered in such cases.
More details at:
http://www.cprogramming.com/debugging/visual-studio-msvc-debugging-NoStepInto.html
It would be a great feature to have something like that also in GDB.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: