From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16672] New: Allow brace expansion on probe points
Date: Fri, 07 Mar 2014 19:26:00 -0000 [thread overview]
Message-ID: <bug-16672-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16672
Bug ID: 16672
Summary: Allow brace expansion on probe points
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: jistone at redhat dot com
As a way to improve brevity in specifying probe points, without requiring
wildcards that may be to broad, we might allow brace expansion similar to
shells.
For example:
process.function("*").{call,return}
=> process.function("*").call, process.function("*").return
process.{function("*").callees,plt}?
=> process.function("*").callees?, process.plt?
{kernel,module("nfs")}.function("nfs*")!
=> kernel.function("nfs*")!, module("nfs").function("nfs*")!
Note the distribution of '?' and '!'. Also, if there are multiple sections of
braces, they will multiply accordingly.
The start of a brace group would only be valid syntax when it immediately
follows 'probe', '.', or ',' where we know there must be a probepoint
component, so it's not ambiguous with the brace starting a probe body. Thus
"probe e{nd,rror}" would not be allowed.
In fact I'd suggest no token-pasting at all, so the branches of the braces must
deal in whole probe components only. Or if not whole components, at least
whole tokens - that way we might still allow something like:
kernel.function({"foo","bar"})
=> kernel.function("foo"), kernel.function("bar")
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-03-07 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 19:26 jistone at redhat dot com [this message]
2015-12-17 21:55 ` [Bug translator/16672] " flu 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-16672-6586@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).