Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: gdb@sourceware.org
Subject: Re: gdbserver ptrace not doing waitpid after attaching to threads?
Date: Sat, 13 Dec 2008 01:07:00 -0000	[thread overview]
Message-ID: <20081213010607.GA21370@caradoc.them.org> (raw)
In-Reply-To: <e394668d0812121521r72e84b3bp29b9e769b78bcbd4@mail.gmail.com>

On Fri, Dec 12, 2008 at 03:21:36PM -0800, Doug Evans wrote:
> Right, new threads could be created after the SETOPTIONS goes into
> affect.  But I'm still unclear whether SETOPTIONS will deliver threads
> that have already been created and exist when gdbserver attaches.

Nope.  You need a different mechanism for that; either libthread_db as
today, or /proc/pid/task/.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2008-12-13  1:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 21:14 Doug Evans
2008-12-12 21:29 ` Daniel Jacobowitz
2008-12-12 23:08   ` Doug Evans
2008-12-12 23:17     ` Daniel Jacobowitz
2008-12-12 23:22       ` Doug Evans
2008-12-13  1:07         ` 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=20081213010607.GA21370@caradoc.them.org \
    --to=drow@false.org \
    --cc=dje@google.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