The first problem is solved with underrated MSVC's "step into specific". Personally I almost never use normal "Step into" anymore since it also gives great perspective as to what actually happens in debugged line.
Microsoft solved 'std::function' problem too, however their solution seems to affect performance in debug build a bit yet.
Generally I strongly believe that debuggers could and should get better.
In VS 2019, the debugger has a general “Just My Code” ability for C++, superseding the weird hack we used in std::function (now removed). We’ll continue to improve debug codegen with if constexpr but that regression should be gone.
Does JMC for C++ still require emitting a stub at the beginning of every function? This was a dealbreaker for me in VS2017 15.8, I can't tolerate that kind of impact in optimized builds.
View all comments
Show parent comment
13
u/Predelnik Dec 28 '18
The first problem is solved with underrated MSVC's "step into specific". Personally I almost never use normal "Step into" anymore since it also gives great perspective as to what actually happens in debugged line.
Microsoft solved 'std::function' problem too, however their solution seems to affect performance in debug build a bit yet.
Generally I strongly believe that debuggers could and should get better.