From: David Carlton <david.carlton@sun.com>
To: gdb <gdb@sourceware.org>
Subject: Re: multithreaded core files
Date: Thu, 25 Jan 2007 20:04:00 -0000 [thread overview]
Message-ID: <yf21wlij2k3.fsf@luai12.SFBay.Sun.COM> (raw)
In-Reply-To: <20070125194840.GA20591@nevyn.them.org> (Daniel Jacobowitz's message of "Thu, 25 Jan 2007 14:48:40 -0500")
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
prev parent reply other threads:[~2007-01-25 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 19:40 David Carlton
2007-01-25 19:48 ` Daniel Jacobowitz
2007-01-25 19:54 ` Neo
2007-01-25 19:57 ` Daniel Jacobowitz
2007-01-25 20:04 ` David Carlton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yf21wlij2k3.fsf@luai12.SFBay.Sun.COM \
--to=david.carlton@sun.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox