Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Lucy Zhang <lucyz@uclink4.berkeley.edu>
Cc: gdb@sources.redhat.com
Subject: Re: Thread signal information
Date: Wed, 24 Jul 2002 09:04:00 -0000	[thread overview]
Message-ID: <20020724160422.GA5346@nevyn.them.org> (raw)
In-Reply-To: <004501ea8fb2$e33da4c0$9a0a0109@zhangl>

On Wed, Jul 24, 2002 at 09:00:43AM -0700, Lucy Zhang wrote:
> Hi,
> 
> I'm constructing an ELF core dump (conversion from a different formatted
> dump). I'm trying to add thread information by using a prstatus struct for
> each thread. I was wondering what should I put for the signal information
> for each thread. Do I even need this info for threads other than the
> faulting thread?

Not really.  I believe that GDB only recognizes the signal in the first
listed thread (or it may have been the last listed thread.... there was
a fix in this area recently, I believe).  First listed (faulting)
certainly makes the most sense, and GDB definitely only cares about one
thread.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-07-24 16:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-24  8:58 Lucy Zhang
2002-07-24  9:04 ` Daniel Jacobowitz [this message]
2002-07-24  9:47   ` Dan Kegel
2002-07-24 11:52     ` Andrew Cagney
2002-07-24 11:57     ` Daniel Jacobowitz
2002-07-24 12:11       ` Dan Kegel
2002-07-25  8:57         ` Lucy Zhang
2002-07-25  9:18           ` Daniel Jacobowitz
2002-07-25 18:28             ` how does GDB find the symbols? Lucy Zhang
2002-07-26 10:03               ` Jim Blandy

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=20020724160422.GA5346@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=lucyz@uclink4.berkeley.edu \
    /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