From: Karim Yaghmour <karim@opersys.com>
To: Muli Ben-Yehuda <mulix@actcom.co.il>
Cc: Fabrizio Morbini <fabrizio.morbini@libero.it>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Tracing each new process...
Date: Thu, 01 Aug 2002 13:25:51 -0400 [thread overview]
Message-ID: <3D496F1F.56A1123A@opersys.com> (raw)
In-Reply-To: 20020801171303.GC7912@alhambra.actcom.co.il
Muli Ben-Yehuda wrote:
> On Thu, Aug 01, 2002 at 01:04:51PM -0400, Karim Yaghmour wrote:
> >
> > Have a look at the Linux Trace Toolkit:
> > http://www.opersys.com/LTT/
>
> syscalltrack, http://syscalltrack.sourceforge.net can do it as
> well. You'll get the notification in user space out of the box, and in
> kernel space with a bit of hacking.
Syscalltrack is only for tracking system calls. If the process creation
was requested from user-space, then indeed syscalltrack will show it.
It won't see kernel threads, among many other things. Not to mention
that it has to play around with the system call table to get its
information.
Now that you mention it, however, it is clear to me that syscalltrack
could definitely use the tracing framework provided by LTT in many
areas. First and foremost, it could get its system call information
using the existing trace hooks provided by LTT. In addition, instead
of implementing yet another event buffering framework, it could
use LTT's trace driver which already provides very efficient buffering.
Yet another reason to include LTT in the kernel.
Karim
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
prev parent reply other threads:[~2002-08-01 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 11:46 Tracing each new process Fabrizio Morbini
2002-08-01 17:04 ` Karim Yaghmour
2002-08-01 17:13 ` Muli Ben-Yehuda
2002-08-01 17:25 ` Karim Yaghmour [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=3D496F1F.56A1123A@opersys.com \
--to=karim@opersys.com \
--cc=fabrizio.morbini@libero.it \
--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