Hide Forgot
+++ This bug was initially created as a clone of Bug #1464085 +++ valgrind currently does not know anything about the CPUID flag added to the HWCAP auxv entry in kernel 4.11. It passes this flag through to applications, but it will then choke when the application uses it, like this: ARM64 front end: branch_etc disInstr(arm64): unhandled instruction 0xD5380000 disInstr(arm64): 1101'0101 0011'1000 0000'0000 0000'0000 ==924== valgrind: Unrecognised instruction at address 0x11f548. ==924== at 0x11F548: init_cpu_features (cpu-features.c:32) ==924== by 0x11F548: dl_platform_init (dl-machine.h:241) ==924== by 0x11F548: _dl_sysdep_start (dl-sysdep.c:231) ==924== by 0x10981B: _dl_start_final (rtld.c:412) ==924== by 0x109AAB: _dl_start (rtld.c:520) This is from a newer glibc (not the one in Red Hat Enterprise Linux). The crashing instruction is the mrs in the glibc startup code: if (hwcap & HWCAP_CPUID) { register uint64_t id = 0; asm volatile ("mrs %0, midr_el1" : "=r"(id)); cpu_features->midr_el1 = id; } else cpu_features->midr_el1 = 0; Perhaps valgrind should mask all the HWCAP bits it knows nothing about. --- Additional comment from Florian Weimer on 2017-06-22 12:21:40 EDT --- Workaround: Run with “LD_HWCAP_MASK=1”. --- Additional comment from Mark Wielaard on 2017-06-23 06:55:45 EDT --- The upstream bug is https://bugs.kde.org/show_bug.cgi?id=381556 arm64: Handle feature registers access on 4.11 Linux kernel or later Fedora valgrind-3.13.0-3.fc27 contains a workaround, see bug https://bugzilla.redhat.com/show_bug.cgi?id=1464211
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.