gdb: Am I a joke to you?
this post was submitted on 28 Feb 2024
1012 points (97.0% liked)
Programmer Humor
33560 readers
612 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
I know this is supposed to be humorous, but there's a reason why these languages can, and are doing what they're doing.
Core dumps are also worth learning about, they're really helpful if you understand them.
My favorite compile error happened while I was taking a Haskell class.
ghc: panic! (the 'impossible' happened)
The issue is plainly stated, and it provides clear next steps to the developer.
I had a similar error, though not from the compiler
Error message just read this should never happen
Ah, good old PlarformIO
The developer must either provide the logging and attach a debugger or go get fucked when a runtime error happens
You can also debug post-mortem with the minidump or the core dump file with WDT on Windows. Great fun and a good way to brush up on your assembly skills
load more comments
(1 replies)
That's not true though. You can get the backtrace and other useful information from the coredump mentioned by the error message by loading it with gdb. Not as good as attaching it to a living process, since you can't see step-by-step what happens leading up to the error, but still quite useful.
load more comments
(1 replies)
are you c++?
let's not act like Java's error log is useful
I think it's pretty useful, be interested to hear your hangups with it though because it's definitely not perfect.
If something goes wrong and I have a stack trace, that plus the type of exception will almost always be enough for me to figure out what's wrong at least as a starting point. I've worked mostly with JVM languages in my career though so maybe I just don't know how bad it actually is.
load more comments
(1 replies)
load more comments
(5 replies)