From: Pavel Machek <pavel@ucw.cz>
To: Muli Ben-Yehuda <mulix@actcom.co.il>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ANN: syscalltrack 0.80 "Tanned Otter" released
Date: Tue, 26 Nov 2002 19:19:47 +0100 [thread overview]
Message-ID: <20021126181947.GB1376@zaurus> (raw)
In-Reply-To: <20021123201015.GD6536@alhambra>
Hi!
> criteria. syscalltrack can operate either in "tweezers mode", where
> only very specific operations are tracked, such as "only track and log
> attempts to delete /etc/passwd", or in strace(1) compatible mode,
> where all of the supported system calls are traced. syscalltrack can
> do things that are impossible to do with the ptrace mechanism, because
> its core operates in kernel space.
What stuff can you do that ptrace can't?
As UML and subterfugue.sf.net shows there's
a *lot* you can do with ptrace.
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2002-11-26 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 20:10 ANN: syscalltrack 0.80 "Tanned Otter" released Muli Ben-Yehuda
2002-11-26 18:19 ` Pavel Machek [this message]
2002-11-26 21:03 ` Muli Ben-Yehuda
2002-11-27 13:29 ` Pavel Machek
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=20021126181947.GB1376@zaurus \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@actcom.co.il \
/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