People often ask me what's wrong with GDB when I say there are no good Linux debuggers. Since I happen to be using it today, here's one reason I often forget to mention: it crashes _constantly_. Today, it has crashed roughly 1 out of every 3 runs of my (non-crashing!) program.
-
Show this thread
-
The fact that it doesn't save breakpoints, watches, or TUI status by default also means you now have to redo all of _that_ every time it crashes. It's just a really bad debugger if you actually care about getting work done. It's not about features, it's about usability.
1 reply 2 retweets 24 likesShow this thread -
You can mitigate some of these problems by getting into GDB "configuration", but I don't _want_ to learn a bunch of random scripting nonsense just to have a usable debugger. I just want it to be stable and remember my state. This should be the default on any debugger!
4 replies 2 retweets 35 likesShow this thread -
Replying to @cmuratori
If you are forced to use gdb and dont the defaults, I’ve found that these sort of premade configs have “Sane Defaults” (tm) and are documented well enough to tunehttps://gist.github.com/chrislongo/3351197 …
3 replies 0 retweets 4 likes
Sadly, those "sane defaults" don't even work with TUI. The prompt becomes garbage and you can't see your own typing :( This is par for the course with GDB in my experience.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.