multithreaded core files

[David Carlton]

On Thu, 25 Jan 2007 14:48:40 -0500, Daniel Jacobowitz <drow@false.org> said:
> On Thu, Jan 25, 2007 at 11:40:42AM -0800, David Carlton wrote:

>> One of my coworkers is looking at a core file from a multithreaded
>> program.  (x86 Linux.)  In this situation, GDB only prints a backtrace
>> from the thread that actually seg faulted; he'd like to see what other
>> threads were doing at the time.

> It should already print all the backtraces.  If it doesn't, the usual
> explanation is that you are using a broken kernel version which does
> not save registers for every thread.  Many 2.4 kernels fit that
> description.

Interesting.  I guess I got stuck in my mind from the 2.4 days that
this doesn't work; checking a recent core file, I see the information
I want.  I'll check with my coworker to see what the vintage is of his
core file...

David Carlton
david.carlton@sun.com