It often happens that I debug a program through step-by-step, In the "step, in the section I'm debugging, to stop every line in it, and when I think I got the current row, just click again.
Actually rejecting this work flow, however, there are library calls if string length calculations or map storage or something similar, debugger will jump into some STL file and continue there. I have to press "jump" to return to the program.
This means: I am actually being interrupted by the interested document, firstly because the code suddenly disappears and the STL source is displayed, and for the second reason I see the button bar and mouse Has to be moved, and when I jump back, I am usually confused.
Is there any way to stop STBL source files from opening the debugger? Some types of black list, or perhaps even more beautiful, some setting somewhere? I've found the "Only my code" setting so far, but it only works for the managed code and I work with the original code.
Good question, always jumping into everything during a debugger is really a big downturn and distraction. Fortunately there is a solution:
Open your Registry Editor, go to
HKLM software \ Microsoft \ VisualStudio \ 10.0 \ NativeDE \ StepOver (If you are on 64 bit machine, then add \ Wow6432Node after software, this shows headache in the past).
Add a new string value (REG_SZ). Name is not so important, I clearly used NoSTL and its value is std \: \:. * = NoStepInto This tells the debugger that there is no step in anything matching the regex, so that it will leave every function (global and square level) in the stad namespace . By using StepInto you can add overrides to specific methods, and you can still use breakpoints. Courses It is also easy to add some of your methods that often take place, but As a result you know the results from the head. There is a more detailed description, more for NoStepInto scattered information.
Comments
Post a Comment