Hide Forgot
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