This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/20416] New: @entry(@perf("foo")) not translated correctly
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 27 Jul 2016 15:59:12 +0000
- Subject: [Bug translator/20416] New: @entry(@perf("foo")) not translated correctly
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20416
Bug ID: 20416
Summary: @entry(@perf("foo")) not translated correctly
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
>From a uprobes .return call, @entry(@perf(...)) doesn't seem to propagate the
logic required to collect the @perf value in the .call synthetic probe:
% sudo stap -e '
global counts
probe perf.sw.cpu_clock.counter("foo") {}
probe process.function("main").return { counts <<< @perf("foo") -
@entry(@perf("foo")) }
' -c /bin/ls
WARNING: never-assigned local variable '__perf_read_foo' (similar:
_entry_tvar_tid, counts): operator '@perf' at <input>:4:74
source: probe process.function("main").return { counts <<< @perf("foo") -
@entry(@perf("foo")) }
The warning is appropriate: if one looks at the -p3 output, the __perf_read_foo
value is only collected in the .return probe, not in the synthetic .call.
--
You are receiving this mail because:
You are the assignee for the bug.