Bug 11966

Summary:	Valgrind segfaults on startup on armhf
Product:	buildroot	Reporter:	andreas.kremser.ext
Component:	Other	Assignee:	unassigned
Status:	RESOLVED MOVED
Severity:	normal	CC:	buildroot, yann.morin.1998
Priority:	P5
Version:	2019.02
Target Milestone:	---
Hardware:	Other
OS:	Linux
Host:		Target:
Build:
Attachments:	Patch to downgrade valgrind to 3.12 Allow Selection of Valgrind on aarch64 buildroot config

Description andreas.kremser.ext 2019-06-18 14:34:25 UTC

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.

Comment 1 andreas.kremser.ext 2019-06-18 14:36:15 UTC

Created attachment 8111 [details]
Patch to downgrade valgrind to 3.12

Comment 2 andreas.kremser.ext 2019-06-18 14:37:11 UTC

Created attachment 8116 [details]
Allow Selection of Valgrind on aarch64

Comment 3 andreas.kremser.ext 2019-06-18 14:39:09 UTC

Created attachment 8121 [details]
buildroot config

Comment 4 Peter Seiderer 2019-07-05 21:35:59 UTC

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?

Comment 5 Yann E. MORIN 2024-06-15 14:49:53 UTC

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!