RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

The py3example currently is python-2.4 specific, and doesn't work with rhel-8's default python3.6:

=======
$ cat ~/WORK/systemtap/testsuite/systemtap.examples/general/tapset/python_local.stpm 

[ ... stuff deleted ... ]

# Set this to the location of the python 3 .so
@define PYTHON3_LIBRARY
%(
  "/usr/lib64/libpython3.4m.so.1.0"
%)
$
=======

Please consider making the example closer to python version agnostic, and/or generally working on rhel8 :)

Note that to install python3-debuginfo on rhel8, one needs to `dnf debuginfo-install platform-python`.

(In reply to Martin Cermak from comment #0)
> The py3example currently is python-2.4 specific
Err - I meant 3.4 specific

At the time that example was written, python 3.4 was the only version of python 3 available. We'll have to figure out how to make it more version agnostic.

The py3example item in the testsuite is not that interesting because it carries its own clunky copy of the python/systemtap tapset bindings, which are of a different flavour than the first class one we actually install.  We should probably just drop this test case and/or adapt the demo.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.