Bug 1467952
Summary: | valgrind: Mask CPUID support in HWCAP on aarch64 | ||
---|---|---|---|
Product: | Red Hat Developer Toolset | Reporter: | Mark Wielaard <mjw> |
Component: | valgrind | Assignee: | Mark Wielaard <mjw> |
Status: | CLOSED ERRATA | QA Contact: | Miloš Prchlík <mprchlik> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | DTS 7.0 RHEL 7 | CC: | fweimer, jakub, kanderso, mbenitez, mcermak, mnewsome, mprchlik, noloader, ohudlick, qe-baseos-tools-bugs |
Target Milestone: | alpha | ||
Target Release: | 7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | devtoolset-7-valgrind-3.13.0-4 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1464085 | Environment: | |
Last Closed: | 2017-10-24 09:46:30 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1464085, 1464211 | ||
Bug Blocks: |
Description
Mark Wielaard
2017-07-05 15:21:27 UTC
Note that this is nor urgent till there is a glibc update that relies on the auxv HWCAP setting on arm64. But programs on arm64 might check the HWCAP themselves and then use some instructions that valgrind doesn't support. Easiest to see what the HWCAP is with/without valgrind is to run: LD_SHOW_AUXV=1 valgrind -q /bin/true | grep HWCAP Which will show the auxv twice, once for valgrind itself, then for /bin/true running under valgrind. Verified with build devtoolset-7-valgrind-3.13.0-4.el7. 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, 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/RHEA-2017:3011 Also see https://bugzilla.redhat.com/show_bug.cgi?id=1464211 . It looks like a similar issue report filed about a month earlier. |