From: Daniel Jacobowitz <drow@false.org>
To: Edward Peschko <esp5@pge.com>
Cc: gdb@sources.redhat.com
Subject: Re: suppressing stepping into standard library functions
Date: Sat, 12 Feb 2005 19:45:00 -0000 [thread overview]
Message-ID: <20050212172417.GA1972@nevyn.them.org> (raw)
In-Reply-To: <20050212061838.GA29624@venus>
On Fri, Feb 11, 2005 at 10:18:38PM -0800, Edward Peschko wrote:
> hey all,
>
> I believe this has to be a FAQ and there must be a good solution
> for this, but I can't find out because of searching being down.. ;-)
>
> Anyways, what I wanted to do is avoid the stepping into standard
> library functions for c++ code - seeing stuff like:
>
> __normal_iterator(const _Iterator& __i) : _M_current(__i) { }
>
> when hitting 'n' in the debugging sessions really obfuscates the flow of
> logic of the program. I'd like to step through my code, and my code only.
>
> Is there a way to configure gdb to avoid stepping into certain
> classes/functions like this?
Not yet - this requires support for inline functions, so that we can
recognize when we're leaving the user code.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-02-12 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 6:52 Edward Peschko
2005-02-12 19:45 ` Daniel Jacobowitz [this message]
2005-02-16 4:34 ` Edward Peschko
2005-02-16 12:04 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050212172417.GA1972@nevyn.them.org \
--to=drow@false.org \
--cc=esp5@pge.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox