3 ms·
I know that GDB is powerful and scriptable and very useful in environment where you don't have anything else. But I'm sorry to say, what you showed wasn't very
by oblio 8y ago
I know that GDB is powerful and scriptable and very useful in environment where you don't have anything else. But I'm sorry to say, what you showed wasn't very discoverable and the UI was faaar from amazing.
I don't know if you've tried it, but whenever you have a bit of time try Visual Studio's (or even Visual Studio Code's) debugger. They're among the best visual debuggers out there. Or IntelliJ's.
You see directly all the variables as you step through code, you can see array contents directly, they're super discoverable, etc.
It's such a shame that there's no glory (or money) to be had in designing CLI/TUIs. I also get the impression that it would be really hard to change things, OSS maintainers have a reputation for being very stubborn about workflow changes (sometimes for good reasons, sometimes not) :(
- camgunz 8y agoGDB's main power is that it's scriptable. You can track down some pretty gnarly bugs with that. You don't necessarily need that capability for languages like JS, because there's far less danger of getting into serious trouble (stack corruption, etc.), so it's hard to appreciate. But yeah, discoverable it is not haha.
- pjmlp 8y agoAll major Java and .NET IDEs have debugging APIs as well. As for the data visualizers, as mentioned, with Java and .NET I can do it with a bit of annotations and the debugger takes it from there. Or in C++'s case when using Visual Studio, a bit of XML describing the metadata.
- camgunz 8y agoOh yeah, totally true. All I meant was GDB's power interface is scripting. I definitely think IDE debuggers are better.