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.
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
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
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.
More like 100 lines of template errors
If only I could show segfaul stack tracetrough looped macros.
It breaks VSCode (it would be hilarious if I wasn’t the author of said macros).
you should get a complete stack trace (complete with values of some function arguments)
The developer must either provide the logging and attach a debugger or go get fucked when a runtime error happens
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.
Well yes, that’s a pretty good way of debugging a third party app but if you are developing something you can have more ease with gdb attached
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
Just load it on the debugger and leave your asm skill gather patina.
are you c++?
No bounds checking, only fast.
My favorite compile error happened while I was taking a Haskell class.
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 happenWhere’s rust?
Rust required you to fix all the errors before running the code.
Runtime errors are still a thing.
Compared to that trio, they are a rarity that make people excited just to spot one.
Runtime errors are rare? Interesting. I guess it depends on how much error handling the dev additionally wants to do.
At least you are getting a dump, count your blessings. Could be worse!
Just hook your app to a debugger and load the dump.
Python: So you used spaces and tabs for indentation? NOW DIE!
Mixing spaces and tabs should be a warcrime.
And in Python, it’s merely a SyntaxCrime.
C#: Time for a treasure hunt! Find the Null Reference Exception. Here’s a map. X marks the spot.
This C++ message has an urgency vibes to it:
“Segmentation fault!! Drop the Nuclear Reactor quick!!”
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++.
Rust seems pretty performant
https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/rust-gpp.html
I meant faster than Python, not faster than Rust. Rust is fast.
Ah. OK. Makes more sense.
There’s embedded rust for a few platforms. Using it on ESPs is fun
If the embedded system is old or poorly-maintained enough, there might be more Rust than you’d think.
Joke on you until the python program segfaults