3 ms·
As much as I love rants like these, the problem with debuggers is discoverability. I have lost track of the number of times that I kill myself debugging someth
by bsder 7y ago
As much as I love rants like these, the problem with debuggers is discoverability.
I have lost track of the number of times that I kill myself debugging something with gdb only to later explain it to some group and somebody says: "LOL, n00b. Why didn't you just use <magic gdb command>?"
Why? Because I didn't know about the magic gdb command and there was no documentation anywhere that would have pointed me to the fact as to that command being exactly what I was busting my head over.
Debuggers are like build systems. You don't diddle with them every day and when you are something is wrong and you're on a deadline.
If people want programmers to appreciate better debugging, we need some good videos of people debugging real problems in real time with debuggers.
- db48x 7y agohttps://www.youtube.com/watch?v=LR0pms_mQuY https://www.youtube.com/watch?v=LR0pms_mQuY was nice to see
- TeMPOraL 7y agoSpeaking of GDB and arcane commands - GDB does have decent documentation. It actually ships with a whole book on how to use it. Try `info gdb` in your terminal (if you get a man page, you're missing info pages; on Ubuntu/Debian, you have to install gdb-doc package). One other way developers suck (myself too often included) is that they don't RTFM. And I don't mean "skim the manpage" RTFM, but actually read the included manual. If you're going to use something day in, day out, it's really worth it to spend the couple of hours required and read the included manual cover-to-cover. It saves a lot of time and frustration in the long run. (I don't use GDB myself all that much, but the last time I had to, I got tired of flailing around; I read the info page cover to cover, and the time investment repaid itself on that single task.)
- roca 7y agoOP here. I get it. I led rr development and even I sometimes find gdb features I never knew about! We explicitly tried hard to make Pernosco discoverable, partly by creating simple but powerful and composable features, and partly using traditional GUI techniques. We definitely haven't fully succeeded, but I think we moved the needle. If you dig through https://pernos.co/about/ https://pernos.co/about/ you can see what we tried, and if you try the demo https://pernos.co/debug/e9UFXkGq__8KQB-N6n59lA/index.html https://pernos.co/debug/e9UFXkGq__8KQB-N6n59lA/index.html you can see how well we succeeded.
- ahaferburg 7y agoFYI none of the images on https://pernos.co/about https://pernos.co/about are working for me. > static.pernos.co has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site. > The issue is most likely with the website, and there is nothing you can do to resolve it.
- roca 7y agoAre you using Firefox Nightly? It had a bug not long ago which was incorrectly blocking those images.
- ahaferburg 7y agoThat's not a problem of debuggers in general, but of some debuggers like gdb and windbg with an arcane text-based interface. I never had any such problem with Visual Studio. Isn't there a GUI for gdb? (I really don't know)