This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: suppressing stepping into standard library functions
- From: Daniel Jacobowitz <drow at false dot org>
- To: Edward Peschko <esp5 at pge dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Sat, 12 Feb 2005 12:24:17 -0500
- Subject: Re: suppressing stepping into standard library functions
- References: <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