Re: How to disable debugger stepping into new (newop.cpp)

From: Johan Nilsson (johan.nilsson_at_newsgroups.nospam)
Date: 09/30/04 

Date: Thu, 30 Sep 2004 11:30:33 +0200

"John Petritis" <Solx@newsgroup.nospam> wrote in message
news:O0HXCFYoEHA.2864@TK2MSFTNGP12.phx.gbl...
> Is there a way to stop the debugger from stepping into some places,
> specifically places like where operator new is defined.
> I know there was a way before Visual Studio.NET, but haven't been able to
> find a way to do it now.
>

There is a possibility to avoid that (but kind of the other way 'round), at
least under VC.NET 2003: When debugging, right-click on the current
statement, select "Step Into Specific" and select where you want to go.

Does that help?

// Johan

Relevant Pages

  • Re: Learning C
    ... I stress that I talking about "stepping through an application". ... And how can stepping through an app be bad? ... I did not step through the code with a debugger. ... "examine", to me, means to study the source code. ...
    (comp.lang.c)
  • Re: Learning C
    ... with a debugger. ... I stress that I talking about "stepping through an application". ... But often loggers affect the app. ... "examine", to me, means to study the source code. ...
    (comp.lang.c)
  • Re: Good debugger?
    ... > Stepping through a script sequence, one line at a time, and watching ... > the variables change values as you do so is a much better approach to ... > think I've ever seen a debugger do that before). ... especially Tkcon) is a single step tool. ...
    (comp.lang.tcl)
  • RE: Step by Step skips large chunks of code
    ... Putting on SP1 the problem occurred. ... the debugger seems to work OK in the main thread ... let us monitor the threads in the Threads window. ... Then start stepping code. ...
    (microsoft.public.vsnet.debugging)
  • Changing source on the fly (Was: Lisp Book(s) in the K&R Style)
    ... Is it possible in CMUCL to change the source when stepping through the ... the source of the very function or loop you are ... curious when I will find it in any lisp debugger. ...
    (comp.lang.lisp)