timbatron

Windbg version for conditional breakpoint should be: bp /w "x == 3" foo

Windbg also supports full c++ expressions and even linq style list comprehension with the "dx" command (instead of the old "??" command). You can even extend that with Natvis or JavaScript. Windbg has a script window built in to help you write extensions. You can do regular scripting stuff as well as extending the type system. For instance, if you have some special type that you want to provide a visualization of, you can write it in js and then whenever you look at the data with dx it'll use your js visualization.

I'd give some examples of what you can do in windbg with that but I'm on my phone. But someone wrote a js extension that could extend the built in type system to include types from an arbitrary c++ header... Or do things like a query for the largest function in a program with a single line of code.

That's demonstrably not true. There are a few specific DLLs that have separate versions shipped in the same OS build (like comctl32), but 99% of DLLs have only x86/x64 versions.

That's understandable. Recent versions of windbg have improved a bit in that regard. Most of the new functionality has been added to a more regular data model that you can browse through, and querying the data can be done using a "linq style" syntax so you can use programming knowledge instead of learning some arcane debugger commands. You still need to know the basics of flow control, but the shortcut keys for those are common with a number of other tools (e.g. F5 to run)

Any specific complaint with JavaScript as the choice? The biggest downside I'm aware of it's the lack of direct support for 64bit numbers. What language would you have preferred? Python maybe?

What's wrong with WinDbg?