this post was submitted on 28 Feb 2024
1010 points (97.0% liked)

Programmer Humor

32558 readers
549 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 18 points 8 months ago (3 children)

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

[–] [email protected] 10 points 8 months ago* (last edited 8 months ago) (1 children)

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.

[–] [email protected] 3 points 8 months ago

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

[–] [email protected] 7 points 8 months ago
[–] [email protected] 6 points 8 months ago (1 children)

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

[–] [email protected] 2 points 8 months ago

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.