23

Is it possible to skip STL Code when using the C++ debugger (native, x64) in Visual Studio 2012? Quite often when debugging C++ code I step into STL code. I expect that the STL code provided by Microsoft is correct - I am not interested in debugging it - I am only interested in debugging my own (self-written) code.

For instacne when setting a break point at this function:

foo(std::make_shared<int>(6));

where foo is defined as:

void foo(std::shared_ptr<int> x)
{
    // do something
}

I do not want to dive into the details of std::make_shared - what I want is to step directly into the function foo. But this seems not to be possible. If the breakpoint at foo(std::make_shared<int>(6)); is reached and I press the 'Step Into' button (or F11) it first steps into the 'memory' header file (STL):

enter image description here

So again I have to press the 'Step Out' button than again the 'Step Into' button to get into the foo function. What I want is to skip the STL related parameter initialization or a possibility to jump directly into the function.

Vertexwahn
  • 7,709
  • 6
  • 64
  • 90
  • On a side note: assuming the [STL is correct is a bad assumption](http://blogs.msdn.com/b/vcblog/archive/2013/06/28/c-11-14-stl-features-fixes-and-breaking-changes-in-vs-2013.aspx). On a more direct note `shift+F11` should be step out, you can simply step out of the STL functions and then step in until you get where you need to be or you can set a breakpoint inside the function. – Mgetz Dec 03 '13 at 13:27

5 Answers5

9

There's Step Into Specific available on the right-click menu:

Step Into Specific

Though for a single argument, I'll more often do Step Into + Step Out + Step Into from the keyboard instead of navigating the menus for Step Into Specific.

An unofficial registry key for always stepping over certain code is described in an MSDN blog post, How to Not Step Into Functions using the Visual C++ Debugger.

xan
  • 7,511
  • 2
  • 32
  • 45
4

With Visual Studio, whenever you are about to step into a function, you can actually right-click onto the statement and select in a cascaded menu called "Step Into Specific" the destination you want to reach. You can then bypass copy constructor/getter/etc. passed as argument to the function. See http://msdn.microsoft.com/en-us/library/7ad07721(v=vs.100).aspx for more information.

HiroshimaCC
  • 486
  • 4
  • 11
2

For new version of Visual Studio like VS2019, we have new chosen: Just my code

https://learn.microsoft.com/en-us/visualstudio/debugger/just-my-code?view=vs-2019

prehistoricpenguin
  • 6,130
  • 3
  • 25
  • 42
1

There used to be a registry key to do that, but this has changed in VS2012:

Visual Studio 2012 (dev11) Everything has changed! Until the VC++ team put something on their blog (feel free to bug them to do this), take a peek at this file:

C:\Program Files[ (x86)]\Microsoft Visual Studio 11.0\Common7\Packages\Debugger\Visualizers\default.natstepfilter

For VS 2013 and 2015, the Just my code setting, known from .NET projects, was extended to work for native C++ too.

Felix Dombek
  • 13,664
  • 17
  • 79
  • 131
-1

Move the STL call (make_shared) outside of foo, and pass the result into foo. Then the breakpoint set on the call to foo should be beyond that STL code. Otherwise could you not put the breakpoint inside the foo definition itself?

MikeD
  • 300
  • 1
  • 7