When upgrading buildroot 2018.02.9 to buildroot 2019.02 valgrind begins to segfault at startup on our armhf Target, while it runs successfully on aarch64. The problem occurs on VALGRIND_VERSION=3.14 changing the recipe to build VALGRIND_VERSION=3.12 with 0004-Fixes-for-musl-libc.patch and without 0003-configure.ac-disable-gcc-march-mips64r2-detection.patch enables valgrind to start successfully again. We use the following toolchain: https://releases.linaro.org/components/toolchain/binaries/7.2-2017.11/arm-linux-gnueabihf/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz Changing the compiler to 7.4-2019.02 or 6.5-2018.12 does not make a difference.
Created attachment 8111 [details] Patch to downgrade valgrind to 3.12
Created attachment 8116 [details] Allow Selection of Valgrind on aarch64
Created attachment 8121 [details] buildroot config
Does an update to valgrind-3.15 (buildroot git) work? Does the same failure happen in case you use an buildroot generated toolchain? Does the failure happen when you use Nulgrind (BR2_PACKAGE_VALGRIND_NULGRIND, '--tool=none')? Any valgrind output before/while segfault?
Thank you for your report. The issue tracker for the Buildroot project has been moved to the Gitlab.com issue tracker: https://gitlab.com/buildroot.org/buildroot/-/issues We are taking this opportunity to close old issues in this old tracker. If you believe your issue is still relevant, please open one in the new issue tracker. Thank you!