suppressing stepping into standard library functions

suppressing stepping into standard library functions

[Edward Peschko]

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?

Ed

Re: suppressing stepping into standard library functions

[Daniel Jacobowitz]

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

Re: suppressing stepping into standard library functions

[Edward Peschko]

> > 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.

so..

Is support for inline functions slated for 6.4? And if I compiled with
-fno-inline, could I get around this?

Ed

Re: suppressing stepping into standard library functions

[Daniel Jacobowitz]

On Tue, Feb 15, 2005 at 08:11:25PM -0800, Edward Peschko wrote:
> > > 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.
> 
> so..
> 
> Is support for inline functions slated for 6.4? And if I compiled with
> -fno-inline, could I get around this?

It's slated for whenever someone does the work, so no :-)

I'm not sure if -fno-inline really suppresses all inlining.  May depend
on your GCC.

-- 
Daniel Jacobowitz
CodeSourcery, LLC