Post funny things about programming here! (Or just rant about your favourite programming language.)
Except the C++ "Core dumped" line is telling you it just wrote a file out with the full state of the program at the time of the crash, you can load it up and see where it crashed and then go and look at what every local variable was at the time of the crash.
Pretty sure you can even step backwards in time with a good debugger to find out exactly how you got to the state you're currently in.
Where does it write the file
I believe it's /var/lib/apport/coredump on Ubuntu.
imagine if it, like, told you this so you didn't have to find out about it via a post on lemmy
imagine if it like, read that file and gave you a stack trace
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.
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
Python: So you used spaces and tabs for indentation? NOW DIE!
Good. Spaces and tabs for indentation should never be mixed in any language other than Whitespace.
Rust developer: I'd like to compile some code
Rust compiler: the fuck you are
The rust compiler holds your hand, wraps you in blankets, makes you hot chocolate, kisses you on the forehead before it gently and politely points out what you did wrong and how you can solve it step-by-step. It would never think of something as heinous as swearing at you, shame on you for insulting my wife's honour like this.
Rust compiler is passive agressive, like:
"There's an error at line 286 because you still don't know how to use the borrow checker after all this time ♥️"
I need a rust compiler in my life 😍
gdb: Am I a joke to you?
Yes. It's a surprisingly bad debugger the more you think about it. I use it largely in assembly and it loves to spit out random errors about memory it tried to access based on the current register state. The shortcuts are kind of dumb.
It certainly works but I wouldn't call it a pleasure to use.
Ex: try disp x/1i $eip often just doesn't work.
Embedded C entered the chat
// I am responsible for every byte of this code and still don't know why this line breaks everything.
https://www.youtube.com/@TsodingDaily
If you're a programmer, or think you might want to be one, I highly recommend this channel. He's a savant at all sorts of low level things, quite funny and entertaining, and does a fantastic job of explaining what's going on.
Imagine unironically praising Java.
The one thing I can say about java; the kinds of people who like Java tend to really like Java. Everyone else just leaves them to it.
And the people hating on it somehow never used any version above 8, which is 10 years old and EOL.
Java is a traditional and conservative language, which has its strong upsides, like the syntax being familiar to many people who haven't used the language before. It's a language that brought us the JVM, gave a job to many people and established fundamentals for other languages to inspire and improve on. If you don't like Java, you can just use another language for the JVM, like Scala, Kotlin or Clojure.
Java is good. Supporting Java legacy is bad
This C++ message has an urgency vibes to it:
"Segmentation fault!! Drop the Nuclear Reactor quick!!"
Average C++ error
gdb ./fuck
r
where
you should get a complete stack trace (complete with values of some function arguments)
No bounds checking, only fast.
There is bounds checking, but it's opt-in. I often enable it on debug builds.
Nevermind that the C++ program is two orders of magnitude faster when completed.
I would love to learn and use Rust but I'm a embedded systems guy. Everything of consequence is C and C++.
The developer must either provide the logging and attach a debugger or go get fucked when a runtime error happens
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.
