From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/6445] extend utrace probes with "system-wide" and target-process syntax
Date: Wed, 30 Jul 2008 15:22:00 -0000 [thread overview]
Message-ID: <20080730152046.6139.qmail@sourceware.org> (raw)
In-Reply-To: <20080422120128.6445.fche@redhat.com>
------- Additional Comments From fche at redhat dot com 2008-07-30 15:20 -------
For purposes of this, it would be sufficient to have two
extensions:
- process("*") syntax
that maps to the task_finder's unrestricted pathname/pid
- target-process syntax
that maps to another task_finder option that restricts its
monitoring to the target() (stap -c/-x) hierarchy
Maybe these two could be the same -- i.e., if someone runs "stap -c/-x",
then process("*").foo (or simpler, process.foo) probes would automagically
be restricted to the target process hierarchy.
Finally, bug #6456 could be a followup to support finer-grained
wildcards as in process("/bin/*").
--
What |Removed |Added
----------------------------------------------------------------------------
Summary|extend utrace probes with |extend utrace probes with
|wildcard and target-process |"system-wide" and target-
|syntax |process syntax
http://sourceware.org/bugzilla/show_bug.cgi?id=6445
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-07-30 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 15:50 [Bug translator/6445] New: extend utrace probes with " fche at redhat dot com
2008-04-30 21:26 ` [Bug translator/6445] " fche at redhat dot com
2008-07-19 18:24 ` [Bug translator/6445] extend utrace probes with wildcard and " fche at redhat dot com
2008-07-30 15:22 ` fche at redhat dot com [this message]
2008-08-11 20:50 ` [Bug translator/6445] extend utrace probes with "system-wide" " dsmith at redhat dot com
2008-08-12 14:46 ` dsmith at redhat dot com
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=20080730152046.6139.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).