This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/10830] New: new pp() variant for source-level probe point name
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 22 Oct 2009 16:28:57 -0000
- Subject: [Bug translator/10830] New: new pp() variant for source-level probe point name
- Reply-to: sourceware-bugzilla at sourceware dot org
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.