You're viewing a single thread.
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
are you c++?
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
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.