From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Denys Vlasenko <dvlasenk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Oleg Nesterov <oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Jan Kratochvil
<jan.kratochvil-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"Dmitry V. Levin" <ldv-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH] ptrace.2: if SEIZE was used, initial auto-attach stop is EVENT_STOP
Date: Wed, 10 Jul 2013 20:50:44 +0200 [thread overview]
Message-ID: <51DDAD04.1000907@gmail.com> (raw)
In-Reply-To: <1372762277-31981-1-git-send-email-dvlasenk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 07/02/13 12:51, Denys Vlasenko wrote:
> For every PTRACE_O_TRACEfoo option, mention that old-style SIGSTOP
> is replaced by PTRACE_EVENT_STOP if PTRACE_SEIZE attach was used.
>
> Mention the same thing again in the description of PTRACE_EVENT_STOP.
Thanks, Denys. Applied. And thanks again for your consistent work
updating this page.
Cheers,
Michael
> Signed-off-by: Denys Vlasenko <dvlasenk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> CC: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> CC: Oleg Nesterov <oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> CC: Jan Kratochvil <jan.kratochvil-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> CC: Dmitry V. Levin <ldv-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
> ---
> man2/ptrace.2 | 32 ++++++++++++++++++++++++++++----
> 1 file changed, 28 insertions(+), 4 deletions(-)
>
> diff --git a/man2/ptrace.2 b/man2/ptrace.2
> index 79d14cc..55c4fe2 100644
> --- a/man2/ptrace.2
> +++ b/man2/ptrace.2
> @@ -340,7 +340,12 @@ Stop the tracee at the next
> .BR clone (2)
> and automatically start tracing the newly cloned process,
> which will start with a
> -.BR SIGSTOP .
> +.BR SIGSTOP ,
> +or
> +.B PTRACE_EVENT_STOP
> +if
> +.B PTRACE_SEIZE
> +was used.
> A
> .BR waitpid (2)
> by the tracer will return a
> @@ -421,7 +426,12 @@ Stop the tracee at the next
> .BR fork (2)
> and automatically start tracing the newly forked process,
> which will start with a
> -.BR SIGSTOP .
> +.BR SIGSTOP ,
> +or
> +.B PTRACE_EVENT_STOP
> +if
> +.B PTRACE_SEIZE
> +was used.
> A
> .BR waitpid (2)
> by the tracer will return a
> @@ -449,7 +459,12 @@ Stop the tracee at the next
> .BR vfork (2)
> and automatically start tracing the newly vforked process,
> which will start with a
> -.BR SIGSTOP .
> +.BR SIGSTOP ,
> +or
> +.B PTRACE_EVENT_STOP
> +if
> +.B PTRACE_SEIZE
> +was used.
> A
> .BR waitpid (2)
> by the tracer will return a
> @@ -1208,7 +1223,16 @@ to finish exiting.
> .B PTRACE_EVENT_STOP
> Stop induced by
> .B PTRACE_INTERRUPT
> -command, or group-stop (only if attached using PTRACE_SEIZE).
> +command, group-stop, or initial ptrace-stop when a new child is attached
> +(only if attached using
> +.BR PTRACE_SEIZE ).
> +Note that unlike other
> +.B PTRACE_EVENT
> +stops, this stop has
> +.I WSTOPSIG(status)
> +other than
> +.B SIGTRAP
> +if it reports a group-stop.
> .LP
> .B PTRACE_GETSIGINFO
> on
>
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-07-10 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 10:51 [PATCH] ptrace.2: if SEIZE was used, initial auto-attach stop is EVENT_STOP Denys Vlasenko
[not found] ` <1372762277-31981-1-git-send-email-dvlasenk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-10 18:50 ` Michael Kerrisk [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=51DDAD04.1000907@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dvlasenk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jan.kratochvil-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=ldv-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.