The debugging workflow is a mess. The visual studio debugger is great. gdb and various front ends for it are all various levels of not so great. There is a b

The debugging workflow is a mess. The visual studio debugger is great. gdb and various front ends for it are all various levels of not so great. There is a better featureset in gdb for the very skilled users to do tricky things, but it's still a bear to learn and get conformable with. Putting the .build-id directory on the network and getting subsitute-path pointing at the right location to debug a continuous integration build from 16 months ago? The hardest part is happening to learn those features exist, and the legwork to make it quick and easy to use is PITA too. Some developers... they just want to open the visual studio debugger and smash "step over/into" until their code works. This isn't the best approach to development and they should probably do a bit more "sit and think about the code" in their development. But professionally I have to support this workflow, it's much smoother in VS than when targeting linux. And it's not an excuse for bad debugging tools either, sometimes you do need to spend a day in the debugger to solve things.