4 ms·

What's wrong with WinDbg?

• Avery3R 8y ago
  The same thing that's wrong with GDB. It's command based and most of the commands are hard to remember.
  • timbatron 8y ago
    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)
• luch 8y ago
  Their scripting engine is probably the worst programming language I have encountered (perl is readable by comparison). That's why I was really extatic when Windbg devs introduced a standard script engine, only to learn later on that was JavaScript ...
  • timbatron 8y ago
    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?
    • luch 8y ago
      Javascript is actually a sane choice for extending a debugger (event-based, async calls builtins, etc.) it's just that I'm not familiar with :p I would have expected Windows to go with Powershell as their scripting engine, that's why I was surprised with Javascript.