Description of problem:
/usr/bin/stap links against four dyninst shared libraries provided by either dyninst or gcc-toolset-11-dyninst.
The four libraries provided by gcc-toolset-11-dyninst are in a directory which stap does not search.
In the absence of a compatible dyninst package, stap does not find those shared libraries without LD_LIBRARY_PATH.

Version-Release number of selected component (if applicable):
systemtap-4.6-4.el8

How reproducible:
Consistently reproducible

Steps to Reproduce:
1. Install a recent compose, with dyninst-12.1.0-1.el8 and systemtap-4.6-4.el8
2. Run /usr/bin/stap

Actual results:
/usr/bin/stap: error while loading shared libraries: libparseAPI.so.11.0: cannot open shared object file: No such file or directory

Expected results:
/usr/bin/stap should not report runtime link errors

Additional info:

https://beaker.engineering.redhat.com/jobs/6599650 demonstrates three workarounds for this issue.

The first recipe ran stap with and without LD_LIBRARY_PATH=/opt/rh/gcc-toolset-11/root/usr/lib64/dyninst/ in the environment.

The second recipe installed dyninst-11.0.0-3.el8, which is compatible with systemtap-4.6-4.el8

The third recipe used systemtap-4.7-1.el8, which is compatible with dyninst-12.1.0-1.el8

The only task failure in that job was in the first recipe, without the LD_LIBRARY_PATH setting (the task with the LD_LIBRARY_PATH setting passed).


Newer composes will eventually prevent this problem, when dyninst and systemtap are back in sync, until the next time they get out of sync.