Bug 1937340 - gcc-toolset-10-valgrind erroneously reports z15 support
Summary: gcc-toolset-10-valgrind erroneously reports z15 support
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: valgrind
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Mark Wielaard
QA Contact: Alexandra Petlanová Hájková
Oss Tikhomirova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-10 12:45 UTC by Alexandra Petlanová Hájková
Modified: 2021-11-10 00:54 UTC (History)
5 users (show)

Fixed In Version: gcc-toolset-11-valgrind-3.17.0-4.el8
Doc Type: Known Issue
Doc Text:
.GCC Toolset 10: Valgrind erroneously reports IBM z15 architecture support Valgrind does not support certain IBM z15 processors features yet, but a bug in GCC Toolset 10 Valgrind causes it to report z15 support when run on a z15-capable system. As a consequence, software that tries to use z15 features when available cannot run under Valgrind. To work around this problem, when running on a z15 processor, use the system version of Valgrind accessible via /usr/bin/valgrind. This build will not report z15 support.
Clone Of:
Environment:
Last Closed: 2021-11-09 18:43:48 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:4263 0 None None None 2021-11-09 18:43:53 UTC

Description Alexandra Petlanová Hájková 2021-03-10 12:45:56 UTC 
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
Comment 2 Frank Ch. Eigler 2021-03-10 14:04:28 UTC 
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.
Comment 13 errata-xmlrpc 2021-11-09 18:43:48 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.