Feature request: traceback on segfaults or exceptions (dreaming aloud) about xeus-cling HOT 5 OPEN

It is not as crazy as it sounds. I have been looking into how to do that, which should be doable in the case of exceptions, less so for segfaults.

from xeus-cling.

On linux, the segmentation fault triggers a sigsegv signal which should result in a core dump containing all the info you need. Some reasons may prevent this core dump to be generated (option disabled in the kernel, redirection to a directory that is not writable); if that cannot be fixed, a solution is to set our own signal handler to generate some information, but there are limitations on what can be done inside such a signal handler.

from xeus-cling.

The core dump is actually printed out by the kernel, but I am not sure how we could generate a traceback from it.

from xeus-cling.

ROOT's interpreter (meaning the actual C++ prompt) does it. I think they trap SIGSEV and execute backtrace and print the result before exiting, as explained here

from xeus-cling.

Could https://github.com/bombela/backward-cpp be used? How can I view crash message for now?

from xeus-cling.