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: Fri, 12 Dec 2008 23:17:00 -0000 [thread overview]
Message-ID: <20081212231626.GA15292@caradoc.them.org> (raw)
In-Reply-To: <e394668d0812121506u55da4a52tcf9a42463e8d2847@mail.gmail.com>
On Fri, Dec 12, 2008 at 03:06:44PM -0800, Doug Evans wrote:
> I mightn't have been clear enough btw. I'm observing these things
> from doing an attach in gdb. Example below.
Oh! Well then. Sounds like it's gotten broken. I know we've fixed
this at least once before.
> This is the first attach that gdbserver does, the one for the process.
> Might it be possible that one has to wait for SIGSTOP even before
> ptrace (SETOPTIONS)? :-)
Yes, that's correct. A bit silly, but correct.
> For clarification, your comment:
>
> > It shouldn't be
> > doing any ATTACH; instead it should be trusting SETOPTIONS to deliver
> > new threads to it via wait.
>
> was for the case where gdbserver starts the program, and not for the
> case where gdbserver attaches to the program, right?
Well, it's for any thread created once the program is running under
gdbserver control. Which amounts to the same thing here.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-12-12 23:17 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 [this message]
2008-12-12 23:22 ` Doug Evans
2008-12-13 1:07 ` Daniel Jacobowitz
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=20081212231626.GA15292@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