Hello,
Most compilers implement an option that allows to get procedure
traceback information upon things like IO errors or floating-point
exceptions, even under high optimization. But it seems SIGSEGV causes
immediate termination. Is there a way to get a traceback after a
SIGSEGV other than running under a debugger? I am sometimes, under rare
conditions which I do not yet understand, getting a SIGSEGV, and it
would be nice if I get a traceback so I can find the problem. But I do
not know how to write my own signal handler (in C) to do this? This on
x86(_64) Linux system.
Thanks,
Aleksandar
|