suppressing stepping into standard library functions

Daniel Jacobowitz drow@false.org
Sat Feb 12 19:45:00 GMT 2005


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



More information about the Gdb mailing list