How to find which thread caused SEGFAULT in a post-mortem gdb session?

c++ gdb segmentation-fault
Martin C. picture Martin C. · Apr 16, 2010 · Viewed 15k times · Source

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

Answer

user184968 picture user184968 · Apr 16, 2010

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?

Related questions

Counter exit code 139 when running, but gdb make it through

My question sounds specific, but I doubt it still can be of a C++ debug issue. I am using omnet++ which is to simulate wireless network. omnet++ itself is a c++ program. I encountered a queer phenomena when I run …

Read More
How do I print the full value of a long string in gdb?

I want to print the full length of a C-string in GDB. By default it's being abbreviated, how do I force GDB to print the whole string?

Read More
How to pass arguments and redirect stdin from a file to program run in gdb?

I usually run a program as : ./a.out arg1 arg2 <file I would like to debug it using gdb. I am aware of the set args functionality, but that only works from the gdb prompt.

Read More