3 ms·
vs debugger and windbg shares the same debugging engine but are geared towards different scenarios. VS Only: rich extensions for languages. GUI debugging(wpf v
by 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 agoThe 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.