3 ms·

Some (all?) of windbg’s functionality is available within the VS debugger. I don’t have VS handy right now; maybe someone else can weigh in... Edit: On first

Some (all?) of windbg’s functionality is available within the VS debugger. I don’t have VS handy right now; maybe someone else can weigh in... Edit: On first glance, this looks informative: https://stackoverflow.com/questions/3438489/using-windbg-from-visual-studio/ https://stackoverflow.com/questions/3438489/using-windbg-fro... . Be sure to read all the answers.

gmueckl 8y ago
Analyzing kernel crash dumps comes tro my mind as a feature that seems windbg only.
v-yadli 8y ago
vs debugger and windbg shares the same debugging engine but are geared towards different scenarios. VS Only: rich extensions for languages. GUI debugging(wpf visualization etc.) Windbg: kernel debugging (drivers etc). Scripting. Better command line interface. Fully expose sos. Dump corrupted heap objects. Better support for C++
- correctifier 8y ago
  The kernel debugger, ntsd and windbg share a debugging engine, and visual studio is a different one. At higher levels, VS is a much nicer experience. If you ever need to get down to lower levels, especially windows libraries and services, the power of the ntsd/windbg engine and its extensions make it much more useful. Knowing it also helps when you eventually need to use KD.