Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Paul Gilliam <pgilliam@us.ibm.com>
Cc: gdb@sources.redhat.com
Subject: Re: ptrace & threads question
Date: Tue, 13 Jul 2004 00:19:00 -0000	[thread overview]
Message-ID: <20040712235805.GA28956@nevyn.them.org> (raw)
In-Reply-To: <200407121636.52089.pgilliam@us.ibm.com>

On Mon, Jul 12, 2004 at 04:36:52PM -0700, Paul Gilliam wrote:
> Hi All,
> 
> 'ptrace' is documented as acting on processes: it takes a PID as an argument. 
> So if we are in a thread environment, where do we get registers for a 
> particular thread? 
> 
> What does the user area mean in a threads environment?

PID on GNU/Linux in this case is what other operating systems call TID. 
It's a kernel process ID and each thread is a kernel process.

> How is this different between NPTL and Linux threads?

Not at all.

-- 
Daniel Jacobowitz


      reply	other threads:[~2004-07-12 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 23:58 Paul Gilliam
2004-07-13  0:19 ` Daniel Jacobowitz [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=20040712235805.GA28956@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=pgilliam@us.ibm.com \
    /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