I'm looking for a way to block the Visual Studio debugger to jump to specific classes and functions when I press F11. Or lock some files so that the IDE does not open them, just step by step (except in cases of exception).
I know this sounds silly, but I use smart pointers and other helper classes, many overloaded operators, a simple expression consists of many function calls that disappear during optimization, so this is not a speed issue, but it is a debugging problem, opening and closing so many files all the time, going through many functions, accidentally leaving the target code, etc.
Here is an example of what I'm talking about:
stepToThisFunction(objectOfIgnoreClass->ignoreFunction());
When the debugger is on this line, pressing F11 should only enter stepToThisFunction , passing through ignoreFunction() or, possibly, any function call from objectOfIgnoreClass .
Invalid equivalent of managed DebuggerStepThrough . I do not want to use the CLI. Just a keyword or macro written before a function / class. I also found something, some changes in the registry key, but that doesn’t seem to be what I’m looking for, or I don’t understand its mechanism (I don’t even understand which registry keys are associated with this), In addition, “put breakpoint "and" start cursor "are not accepted.
source share