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.
-
-
just sitting here waiting for the hilariously obserd responses that are soon to come from linux zealots.
-
In how many cases you need gdb and cannot use clang/llvm and lldb to develop and debug? Honest question
End of conversation
New conversation -
-
-
This Tweet is unavailable.
-
I don't know, but DOES WANT
End of conversation
-
-
-
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 …
-
Ugh don’t like*
End of conversation
New conversation -
-
-
What is your view in Front-ends for GDB like (don't kill the messenger) Atom or VSCode? AFAIK watches are a compiler-frontend feature, maybe some of the others too.
-
I did try VSCode, but unless they have made significant improvements, it was more of a toy debugger at the time. You could not, for example, view source and assembly together. So I didn't give it any serious consideration.
- Show replies
New conversation -
-
-
That's bizarre! I've used http://cgdb.github.io for the last 2 years, and while I don't think it's usable by default at all, It has not crashed on me once (while Visual Studio crashing on me at least once a day).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.