From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/6897] stap should assert valid PIDs for process(PID) probes
Date: Wed, 17 Sep 2008 13:49:00 -0000 [thread overview]
Message-ID: <20080917134815.18095.qmail@sourceware.org> (raw)
In-Reply-To: <20080917112256.6897.srikar@linux.vnet.ibm.com>
------- Additional Comments From fche at redhat dot com 2008-09-17 13:48 -------
I changed the summary line to better reflect the concern.
If this was desirable (I'm unsure), it could be done by
running a test after the task_finder_start work that looks
through all utrace (+ uprobe) probe point specs. Any
pid-filtered ones that have not become activated could
be treated as a cause for a startup error.
OTOH, we silently permit module("foo") probes where the
foo module is not actually loaded at run time.
--
What |Removed |Added
----------------------------------------------------------------------------
Summary|stap not resolving |stap should assert valid
|process(pid).statements |PIDs for process(PID) probes
|properly. |
http://sourceware.org/bugzilla/show_bug.cgi?id=6897
------- 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-09-17 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 11:24 [Bug runtime/6897] New: stap not resolving process(pid).statements properly srikar at linux dot vnet dot ibm dot com
2008-09-17 13:49 ` fche at redhat dot com [this message]
2008-09-17 14:48 ` [Bug runtime/6897] stap should assert valid PIDs for process(PID) probes dsmith at redhat dot com
2008-09-18 6:05 ` srikar at linux dot vnet dot ibm dot com
[not found] <bug-6897-6586@http.sourceware.org/bugzilla/>
2014-06-24 19:12 ` ajakop at redhat dot com
2014-08-16 20:44 Torsten Polle
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=20080917134815.18095.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).