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
You can use command thread apply all bt or thread apply all bt full to get backtraces of all threads. Might be useful.
By the way if you get rid of you handler will your OS create a core file?
来源：https://stackoverflow.com/questions/2652944/how-to-find-which-thread-caused-segfault-in-a-post-mortem-gdb-session