From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/10466] stap -L misrepresents variables available to multi-probe aliases
Date: Thu, 29 Oct 2009 23:30:00 -0000 [thread overview]
Message-ID: <20091029232956.28634.qmail@sourceware.org> (raw)
In-Reply-To: <20090731010425.10466.jistone@redhat.com>
------- Additional Comments From jistone at redhat dot com 2009-10-29 23:29 -------
(In reply to comment #1)
> Created an attachment (id=4336)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=4336&action=view)
> patch
>
> It's difficult to discriminate between multi probes like signal.* and one name
> with several expanded probe alias like signal.send. Moreover the variable list
> is in string stream, to make intersection is a little arduous.
It doesn't have to stay as a string stream though. The probes could instead
keep a set<string> of "name:type", to be reconciled at the higher level.
> Maybe [listing expansions separately] can be a good choice.
I don't think it's right to make the user figure out the common variables...
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10466
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-10-29 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 1:04 [Bug tapsets/10466] New: " jistone at redhat dot com
2009-10-29 8:53 ` [Bug tapsets/10466] " wenji dot huang at oracle dot com
2009-10-29 23:30 ` jistone at redhat dot com [this message]
2009-11-03 5:37 ` wenji dot huang at oracle dot com
2009-11-03 19:42 ` jistone at redhat dot com
2009-11-04 3:09 ` wenji dot huang at oracle dot com
2009-11-04 19:21 ` jistone 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=20091029232956.28634.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).