[Bug tapsets/26536] New: make it possible to have third-party add-on tapsets without conflicting with stap standard tapset
fche at redhat dot com
sourceware-bugzilla@sourceware.org
Tue Aug 25 15:59:48 GMT 2020
https://sourceware.org/bugzilla/show_bug.cgi?id=26536
Bug ID: 26536
Summary: make it possible to have third-party add-on tapsets
without conflicting with stap standard tapset
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
systemtap installs its own tapset/ under $prefix/..., aka. $SYSTEMTAP_TAPSET.
Third party packages like ruby and python and .... also install extension
tapsets under the same path. This is a problem if one has a private copy of
systemtap installed under a different $prefix, because then these third-party
tapsets are inaccessible. Setting
$SYSTEMTAP_TAPSET=/usr/share/systemtap/tapset probably doesn't work for these,
because the distro version would not match the stap-version runtime/ or
translator.
So we need to somehow separate the two: third-party tapsets and
stap-accompanying tapsets.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Systemtap
mailing list