Yes, that is why Visual Studio team started doing talks about how to use the debugger.
They started to realize that there were many developers doing feature requests for stuff Visual Studio already supports.
Do you know how to record all backtraces of all threads and child processes with the VS debugger? Just curious. I did it lately with gdb [0], but with a bit guerrilla method. It was my try at localizing the origins of dreadlocks. I would appreciate pointers for something better for dreadlocks, but the original question still stands.
I understand that what I did would be a bit close to a poor man's reversible debugger.
[0] https://gist.github.com/hadrianw/5b8d33a4b353c49e7dbd6eb55f8...
I usually make use of the tasks and thread viewers.
https://docs.microsoft.com/en-us/visualstudio/debugger/debug...
https://docs.microsoft.com/en-us/visualstudio/debugger/map-m...
Otherwise Intellitrace is the way to go.
https://docs.microsoft.com/en-us/visualstudio/debugger/intel...
Me, I'm lazy, so I lean on my tools to make my life easy. And there's some fantastic tooling out there; the biggest problem is usually discovering that a helpful feature exists and how to use it effectively.