Automatically show stack trace on segfault - Githubissues

jacg / nain4

An API that makes it easier to write Geant4 application code.

https://jacg.github.io/nain4/

2 stars 3 forks source link

Automatically show stack trace on segfault #164

Open jacg opened 11 months ago

jacg commented 11 months ago

... so that even users who have never heard of debuggers, immediately get something far more informative, when the program crashes.

Even for those who are familiar with debuggers, immediately being shown where the problem occurred, without having to fire up the debugger (and re-run the program, if, as is likely these days, no core dump was kept, or the user doesn't know where it was kept).

Of course, for it to be truly useful we will need to solve #28.

Some relevant links:

https://www.gnu.org/software/libc/manual/html_node/Backtraces.html
https://chromium.googlesource.com/breakpad/breakpad (available in nixpkgs) This one seems to rely on a server to provide information about crashes in stripped binaries, or something like that:
- https://chromium.googlesource.com/breakpad/breakpad/+/HEAD/docs/getting_started_with_breakpad.md
https://www.boost.org/doc/libs/master/doc/html/stacktrace.html (available in nixpkgs)

jacg commented 11 months ago

We could add a just dbg (or just gdb and just lldb) recipe which runs the program directly in the (specified) debugger.