Hi,
In my application I handle SIGSEG to produce a backtrace and call abort()
to generate a core dump.
If I now run a gdb-post-mortem analysis of the core, the thread which caused the SEGFAULT is no longer visible. Is there anything I can do so I see the cause for the SEGFAULT?
Best regards, Martin