title: How to find which thread caused SEGFAULT in a post-mortem gdb session?
body: <p>In my application, I handle SIGSEG to produce a backtrace and call <code>abort()</code> to generate a core dump.</p>
  <p>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?</p>