C++ Moment

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.

let's not act like Java's error log is useful

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.

Python: So you used spaces and tabs for indentation? NOW DIE!

Rust developer: I'd like to compile some code

Rust compiler: the fuck you are

gdb: Am I a joke to you?

Embedded C entered the chat

Imagine unironically praising Java.

This C++ message has an urgency vibes to it:

"Segmentation fault!! Drop the Nuclear Reactor quick!!"

gdb ./fuck
r
where

you should get a complete stack trace (complete with values of some function arguments)

No bounds checking, only fast.

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++.

Joke on you until the python program segfaults

The developer must either provide the logging and attach a debugger or go get fucked when a runtime error happens

https://media.tech.lgbt/media_attachments/files/111/999/538/786/673/573/original/f7c07158c10abb62.png

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.

More like 100 lines of template errors

Where's rust?

At least you are getting a dump, count your blessings. Could be worse!

Just hook your app to a debugger and load the dump.

Permanently Deleted

C#: Time for a treasure hunt! Find the Null Reference Exception. Here's a map. X marks the spot.

puts me in mind of the old guru meditation error messages that popped up in the stone knives and bearskins era of computing.

Why doesn't JavaScript have tracebacks?