From: "Indan Zupancic" <indan@nul.nu>
To: "Pedro Alves" <pedro@codesourcery.com>
Cc: "Denys Vlasenko" <vda.linux@googlemail.com>,
"Denys Vlasenko" <dvlasenk@redhat.com>,
"Oleg Nesterov" <oleg@redhat.com>, "Tejun Heo" <tj@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Make PTRACE_SEIZE set ptrace options specified in 'data'
Date: Tue, 13 Sep 2011 10:04:46 +0200 [thread overview]
Message-ID: <9b86bd67bedfcd3d4e592a419d190b90.squirrel@webmail.greenhost.nl> (raw)
In-Reply-To: <201109101312.39256.pedro@codesourcery.com>
Hello,
On Sat, September 10, 2011 14:12, Pedro Alves wrote:
>
> I happen to know gdb's code quite well. ;-)
In that case, could you explain why gdb isn't using WCONTINUED
notifications for selective thread wakeup instead of trying to
achieve the same at group stop time?
Background thread: https://lkml.org/lkml/2011/9/7/294
Basically the only argument against making ptrace not automatically
continue group stopped tasks was that gdb uses that to resume one
thread instead of all. But it does this by letting the tasks hang in
trapped state at group stop notification time, breaking normal group
stops. If it would instead use the group continuation notification,
gdb would never need to directly interfere with group stops.
I find PTRACE_LISTEN an ugly solution to this problem and am searching
for something nicer.
Greetings,
Indan
next prev parent reply other threads:[~2011-09-13 8:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 18:22 Denys Vlasenko
2011-09-08 19:24 ` Oleg Nesterov
2011-09-09 11:12 ` Pedro Alves
2011-09-09 12:28 ` Denys Vlasenko
2011-09-09 13:15 ` Pedro Alves
2011-09-09 16:30 ` Oleg Nesterov
2011-09-09 16:55 ` Denys Vlasenko
2011-09-09 17:09 ` Pedro Alves
2011-09-09 17:18 ` Oleg Nesterov
2011-09-09 20:03 ` Denys Vlasenko
2011-09-10 11:19 ` Pedro Alves
2011-09-10 11:40 ` Denys Vlasenko
2011-09-10 12:12 ` Pedro Alves
2011-09-10 15:36 ` Pedro Alves
2011-09-13 7:45 ` Indan Zupancic
2011-09-13 8:04 ` Indan Zupancic [this message]
2011-09-10 23:34 ` Tejun Heo
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=9b86bd67bedfcd3d4e592a419d190b90.squirrel@webmail.greenhost.nl \
--to=indan@nul.nu \
--cc=dvlasenk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pedro@codesourcery.com \
--cc=tj@kernel.org \
--cc=vda.linux@googlemail.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
Powered by JetHome