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 21:29:00 -0000 [thread overview]
Message-ID: <20081212212838.GA8833@caradoc.them.org> (raw)
In-Reply-To: <20081212211315.57CE01C7A79@localhost>
On Fri, Dec 12, 2008 at 01:13:15PM -0800, Doug Evans wrote:
> Why isn't gdbserver waiting for a SIGSTOP after attaching to threads?
It's supposed to be. At one point it definitely was, though it might
have broken recently and been saved by luck. We attached the thread
but did not mark it stopped
> I've run gdbserver under strace and see that gdbserver is essentially doing
> ptrace (ATTACH), ptrace (SETOPTIONS), ptrace (GETREGS) on threads
> with no intervening waitpid.
Is this current source? A vaguely current kernel? It shouldn't be
doing any ATTACH; instead it should be trusting SETOPTIONS to deliver
new threads to it via wait.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-12-12 21:29 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 [this message]
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
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=20081212212838.GA8833@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