From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/6826] New: shorthand or variable for probed executable's path
Date: Fri, 08 Aug 2008 21:26:00 -0000 [thread overview]
Message-ID: <20080808212540.6826.jkenisto@us.ibm.com> (raw)
Suppose the program I'm probing has a really long pathname, or at least one that
I'd rather not retype or copy&paste a lot. Is there some way to arrange it so
every probe definition doesn't have to start with
probe process("/a/really/long/pathname").whatever ...
?
BTW, I don't consider this a viable solution:
probe process(@1).whatever ...
stap xxx.stp /a/really/long/pathname
--
Summary: shorthand or variable for probed executable's path
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: jkenisto at us dot ibm dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=6826
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-08-08 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 21:26 jkenisto at us dot ibm dot com [this message]
2008-08-08 22:06 ` [Bug translator/6826] " joshua dot i dot stone at intel dot com
2008-08-09 14:37 ` fche at redhat dot com
2008-08-09 18:01 ` fche at redhat dot com
2010-04-19 12:45 ` 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=20080808212540.6826.jkenisto@us.ibm.com \
--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).