News for hackers. Stuff that matters.
Re:RemedyBG: Replacing the Visual Studio Debugger by asveikau on Friday March 08, 2019 @10:28PM (#19344258)
I personally like windbg more on windows. It's a light standalone tool not tied to a behemoth editor and build system. It's more command line oriented. Remote support is a bit more flexible. It's better at debugging without symbols too.
Re:RemedyBG: Replacing the Visual Studio Debugger by WalterGR on Friday March 08, 2019 @10:32PM (#19344270)
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-fro... . Be sure to read all the answers.

Re:RemedyBG: Replacing the Visual Studio Debugger by v-yadli on Saturday March 09, 2019 @01:58AM (#19344895)
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++

Re:RemedyBG: Replacing the Visual Studio Debugger by correctifier on Saturday March 09, 2019 @03:03AM (#19345045)
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.

Re:RemedyBG: Replacing the Visual Studio Debugger by gmueckl on Saturday March 09, 2019 @12:41AM (#19344692)
Analyzing kernel crash dumps comes tro my mind as a feature that seems windbg only.