From: "Charles P. Wright" <cwright@cs.sunysb.edu>
To: Daniel Jacobowitz <dan@debian.org>
Cc: blaisorblade@yahoo.it, Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Michael Kerrisk <mtk-manpages@gmx.net>
Subject: Re: [RFC] Proposed manpage additions for ptrace(2)
Date: Thu, 16 Mar 2006 16:16:38 -0500 [thread overview]
Message-ID: <1142543798.3284.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20060316200201.GA20315@nevyn.them.org>
On Thu, 2006-03-16 at 15:02 -0500, Daniel Jacobowitz wrote:
> > PTRACE_SYSEMU, PTRACE_SYSEMU_SINGLESTEP
> > For PTRACE_SYSEMU, continue and stop on entry to the next
> > syscall, which will not be executed. For PTRACE_SYSEMU_SIN-
> > GLESTEP, so the same but also singlestep if not a syscall.
>
> I think this is right; I had nothing to do with these :-)
I didn't have anything to do with it, but this description is correct
(if a bit confusing). I think that you should explicitly say (assuming
that Paolo does not have any objections):
PTRACE_SYSEMU only makes sense at a call's exit, not at entry.
PTRACE_SYSEMU is only practical if you want to emulate all of a
process's system calls (as is done in UML), because you can not examine
the process's registers before making the decision to emulate a call.
Charles
next prev parent reply other threads:[~2006-03-16 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 9:12 [RFC] Proposed manpage additions for ptrace(2) Chuck Ebbert
2006-03-15 20:39 ` Michael Kerrisk
2006-03-16 20:02 ` Daniel Jacobowitz
2006-03-16 21:16 ` Charles P. Wright [this message]
2006-03-17 18:46 ` Blaisorblade
2006-03-18 20:37 ` Charles P. Wright
2006-03-25 0:07 ` Blaisorblade
-- strict thread matches above, loose matches on Subject: below --
2006-03-17 11:44 Chuck Ebbert
2006-03-17 20:04 ` 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=1142543798.3284.6.camel@localhost.localdomain \
--to=cwright@cs.sunysb.edu \
--cc=76306.1226@compuserve.com \
--cc=blaisorblade@yahoo.it \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
/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