tags:

views:

259

answers:

1

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

+1  A: 

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?

skwllsp
Currently I use the handler to write a backtrace to stderr, so I have anything, as I could not get anything out of the core-file. I have to try if the default handler will produce "better" core dumps.
Martin C.
`ulimit -c unlimited` and see what core you will get without any handler.
skwllsp