Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
valgrind -q --tool=none /usr/bin/python3 -c 'print("hello")'
==2875567== 
==2875567== Process terminating with default action of signal 4 (SIGILL): dumping core
==2875567==  Illegal opcode at address 0x4FA90E6
==2875567==    at 0x4FA90E6: __memmove_arch13 (in /usr/lib64/libc-2.28.so)
==2875567==    by 0x4C11975: ??? (in /usr/lib64/libpython3.6m.so.1.0)
==2875567==    by 0x4C1344D: PyList_Sort (in /usr/lib64/libpython3.6m.so.1.0)
==2875567==    by 0x4CFA0CD: _PySys_Init (in /usr/lib64/libpython3.6m.so.1.0)
==2875567==    by 0x4D059CD: _Py_InitializeEx_Private (in /usr/lib64/libpython3.6m.so.1.0)
==2875567==    by 0x4D0638B: Py_Main (in /usr/lib64/libpython3.6m.so.1.0)
==2875567==    by 0x108CBB: main (in /usr/libexec/platform-python3.6)
Illegal instruction (core dumped)


Version-Release number of selected component (if applicable):
gcc-toolset-10-valgrind-3.16.0-4.el8

While it would certainly be desirable from a maintenance viewpoint to have
the fix backported from the baseos version of valgrind, from a user viewpoint
it doesn't seem worth it at this stage.  The baseos version works, so a
"known issue" can easily direct them to that one, if they encounter this
problem.

So while we could turn the process crank, and try to get an exception process
started, the availability of a simple workaround makes that effort/disruption
unnecessary.

Reassigning this to 8.5.0.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: gcc-toolset-11-valgrind), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4263