From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/13450] get rid of most/all probe-alias "?" (optional) markup
Date: Tue, 29 Nov 2011 19:03:00 -0000 [thread overview]
Message-ID: <bug-13450-6586-iQk2HDgB0u@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13450-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13450
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jistone at redhat dot com
--- Comment #1 from Josh Stone <jistone at redhat dot com> 2011-11-29 17:18:48 UTC ---
(In reply to comment #0)
> It quietly fails when the underlying bar probe point is not present.
That's not true:
$ stap -e 'probe foo = bar ? {} probe foo {}' -p2
semantic error: no match while resolving probe point foo
Pass 2: analysis failed. Try again with another '--vp 01' option.
The optional tag on the alias allows a user to possibly match the probe with a
wildcard, but carry on if it doesn't resolve.
$ stap -e 'probe bar = foo ? {} probe b* {}' -p2 -u
# probes
begin /* <- b* */
vs.
$ stap -e 'probe bar = foo {} probe b* {}' -p2 -u
semantic error: probe point mismatch at position 0 (alternatives: __nfs
__scheduler __signal __tcpmib __vm _linuxmib _signal _sunrpc _syscall _vfs bar
begin begin(number) end end(number) error error(number) generic ioblock
ioblock_trace ioscheduler ioscheduler_trace ipmib irq_handler kernel kprobe
kprocess linuxmib module(string) nd_syscall netdev never nfs nfsd perf process
process(number) process(string) procfs procfs(string) scheduler scsi signal
socket softirq stap staprun sunrpc syscall tcp tcpmib timer tty udp vfs vm
workqueue): identifier 'foo' at <input>:1:13 while resolving probe point foo
source: probe bar = foo {} probe b* {}
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-11-29 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 17:11 [Bug tapsets/13450] New: " fche at redhat dot com
2011-11-29 19:03 ` jistone at redhat dot com [this message]
2013-05-15 14:52 ` [Bug tapsets/13450] " fche 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=bug-13450-6586-iQk2HDgB0u@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).