From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10830] New: new pp() variant for source-level probe point name
Date: Thu, 22 Oct 2009 16:29:00 -0000 [thread overview]
Message-ID: <20091022162856.10830.fche@redhat.com> (raw)
As it is, pp() from within a process.mark probe returns something like
process(..).statement(23748234), whereas the original mark() would be
rather more informative appropriate.
One problem is that the current rewriting machinery
(sdt_query::handle_query_module) creates a synthetic probe that maintains
no relationship to the original one. If it created an alias_derived_probe,
then at least a aliaswise derivation chain would be preserved.
Considering that existing aliases like "syscall.open" result in pp()'s that
are the most-expanded, 'kernel.function("...")' strings, we may also need
another pp() variant that gives the least-expanded (but including wildcard
expansions) probe point -- i.e., the topmost alias name. For this function,
say, pp1(), we could return syscall.open and indeed process("...").mark("...").
The future data emitted into the generated C code to enable pp1() could be
conditionally compiled in iff pp1() is present in the script code -- kind of
like what we do for STP_NEED_SYMBOL_DATA etc.
--
Summary: new pp() variant for source-level probe point name
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10830
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-10-22 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 16:29 fche at redhat dot com [this message]
2009-10-22 17:58 ` [Bug translator/10830] " jistone at redhat dot com
2009-10-22 18:05 ` jistone at redhat dot com
2010-01-18 20:16 ` fche at redhat dot com
2010-03-16 18:20 ` jistone at redhat dot com
2010-06-23 11:43 ` jistone at redhat dot com
2010-06-23 16:43 ` mjw at redhat dot com
2010-06-23 23:09 ` przemyslaw at pawelczyk dot it
2010-06-24 7:10 ` fche at redhat dot com
2010-06-24 18:47 ` 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=20091022162856.10830.fche@redhat.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).