From: Pavel Machek <pavel@ucw.cz>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Roland McGrath <roland@redhat.com>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: What is ptrace flag PT_TRACESYSGOOD for?
Date: Wed, 15 Mar 2006 00:00:56 +0100 [thread overview]
Message-ID: <20060314230056.GA1579@elf.ucw.cz> (raw)
In-Reply-To: <200603140531_MC3-1-BAA0-B3C3@compuserve.com>
On Út 14-03-06 05:26:52, Chuck Ebbert wrote:
> I am trying to document PTRACE_SETOPTIONS and I can't figure out what
> the option PTRACE_O_TRACESYSGOOD is used for. Google is no help;
> I can't find an explanation for _why_ it's there. All I can see is that
> it causes ptrace() to deliver syscall stops with SIGTRAP | 0x80
> instead of just SIGTRAP and it can be used with PTRACE_SYSEMU.
Yes.. and unless you deliver ptrace() syscall stops with different
signal, you can't tell difference between syscall stop and real
SIGTRAP.
See subterfugue.org for example user.
Basically we'd like all the new users to set PTRACE_O_TRACESYSGOOD.
Pavel
--
181:
next prev parent reply other threads:[~2006-03-14 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 10:26 What is ptrace flag PT_TRACESYSGOOD for? Chuck Ebbert
2006-03-14 14:01 ` Charles P. Wright
2006-03-14 20:00 ` Jeff Dike
2006-03-14 23:00 ` Pavel Machek [this message]
2006-03-15 1:13 ` Jeff Dike
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=20060314230056.GA1579@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=torvalds@osdl.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