[Bug translator/21833] New: odd 'confusing usage, consider @entry($vmf->address) in .return probe' warnings in tapset/linux/memory.stp
dsmith at redhat dot com
sourceware-bugzilla@sourceware.org
Tue Jul 25 21:06:00 GMT 2017
https://sourceware.org/bugzilla/show_bug.cgi?id=21833
Bug ID: 21833
Summary: odd 'confusing usage, consider @entry($vmf->address)
in .return probe' warnings in tapset/linux/memory.stp
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
Target Milestone: ---
With HEAD systemtap:
====
# stap -p4 testsuite/buildok/memory-all-probes.stp
WARNING: cannot probe .return of 1 inlined functions do_brk
WARNING: confusing usage, consider @entry($addr) in .return probe: identifier
'$addr' at /usr/local/share/systemtap/tapset/linux/memory.stp:194:15
source: address = $addr
^
WARNING: confusing usage, consider @entry($len) in .return probe: identifier
'$len' at :195:14
source: length = $len
^
WARNING: confusing usage, consider @entry($start) in .return probe: identifier
'$start' at :211:15
source: address = $start
^
WARNING: confusing usage, consider @entry($oc->chosen) in .return probe:
identifier '$oc' at :249:16
source: task = $oc->chosen
^
WARNING: confusing usage, consider @entry($vmf->address) in .return probe:
identifier '$vmf' at :148:31
source: address = @choose_defined($vmf->address,$address)
^
in expansion of macro: operator '@value_if_defined' at
/usr/local/share/systemtap/tapset/choose_defined.stpm:3:35
source: ( @defined(@value_if_defined) ? (@value_if_defined) :
(@alternate) )
^
in expansion of macro: operator '@choose_defined' at
/usr/local/share/systemtap/tapset/linux/memory.stp:148:15
source: address = @choose_defined($vmf->address,$address)
... stuff deleted ...
====
Those warnings are quite odd, since the probes it is complaining about aren't
return probes, they are entry probes.
These are just warnings, but this is still quite confusing.
(Note that these warnings happen before and after the bpf merge, so it isn't
the culprit.)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Systemtap
mailing list