Debugging

[Greg Decos]

Is there any way to bypass stepping through the standard libraries when
debugging?

Thanks

 

[William DePalo [MVP VC++]]

Is there any way to bypass stepping through the standard libraries when
debugging?

Well, how did you get there? If you told the debugger to "step into" rather
than "step over" then it did your bidding. If you find yourself somewhere
that you don't want to be then you can "step out".

Just by the way, the debug commands I mentioned are available from then menu
as well as via key-bindings.

Regards,
Will

 

[Greg Decos]

I am looking for something similar to the system.diagnostics
debuggerstepthroughattribute

Thanks
Greg

 

[Hendrik Schober]

Is there any way to bypass stepping through the standard libraries when
debugging?

Well, how did you get there? [...]

It happens to me this way:

void f(const std::vector<X>& v)
{
g( v.size() );
}

When you're on the call to 'g()' and
want to step into it, you first have
to step into 'std::vector<>::size()'.
This can be annoying, although I would
not turn it of as occasionally I want
to go there.
I have two ways to deal with that: I
jump out immediately as Will suggested
(that's <Shift>+<F11> with e.g. VC-
Profile). The disadvantage is, that
this leaves many std lib headers open
and when you have code like this

g( v.begin(), v.end(), l.size() );

you have to do it multiple times.
So often I open the disasembler windows
(<Alt>+<F8>), look for the call I want
to step into, goto this (Curser in its

Regards,
Will

Schobi

--
(e-mail address removed) is never read
I'm Schobi at suespammers dot org

"Sometimes compilers are so much more reasonable than people."
Scott Meyers

 

[William DePalo [MVP VC++]]

It happens to me this way:

void f(const std::vector<X>& v)
{
g( v.size() );
}

I'd put the break at the entry to g. In any event, I can't vouch for the
accuracy of the info there, but this link may help the OP stay out of places
he doesn't want to go:


http://dabbler.typepad.com/ooze/2003/12/nostepinto_for_.html

Regards,
Will

 

[Hendrik Schober]

[...]
I'd put the break at the entry to g. [...]

The problem is when you step through the
code and then decide you want to step
into 'g()', there is no breakpoint. And
finding 'g()' to set one might be even
more hassle than going into 'v.size()'.

http://dabbler.typepad.com/ooze/2003/12/nostepinto_for_.html

There was a discussion reagrding this in
this group, I think, last week. The problem
discussed was that this feature apparently
is disabled for Win2k.

Regards,
Will

Schobi

--
(e-mail address removed) is never read
I'm Schobi at suespammers dot org

"Sometimes compilers are so much more reasonable than people."
Scott Meyers