[ekr]

How does this compare to WinDBG, which already seems fairly mature? Why would I switch to this? (if you ask me, the problem of FOSS doesn't come into play here, since Windows itself is a closed platform).

And indeed, a similar GUI-based debugger for Linux would be awesome as well.

[asveikau]

To me the strength of windbg is not the 1990s style Multiple Document Interface UI. It's the fact that the commands are so terse and powerful. Once you get over the (steep, I'll admit) learning curve, you get a lot done without typing very much. I find gdb a lot more painful to get around for even simple stuff.

The remote debugging support is also phenomenal, though you need a culture to support it. I've only seen it work really well on the MS campus.

[userbinator]

> if you ask me, the problem of FOSS doesn't come into play here, since Windows itself is a closed platform

There are many Windows users who prefer to use FOSS despite the OS itself not being so, and have more pragmatic reasons for using Windows over some other (possibly FOSS) OS.

[WalterBright]

Windbg was broken on Win 7, in that it no longer is able to walk the stack by following [EBP]. If I want to get a call stack, I have to use Windbg on Windows XP.