[Buildroot] [Bug 11966] New: Valgrind segfaults on startup on armhf

[Buildroot] [Bug 11966] New: Valgrind segfaults on startup on armhf

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=11966

            Bug ID: 11966
           Summary: Valgrind segfaults on startup on armhf
           Product: buildroot
           Version: 2019.02
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: andreas.kremser.ext at b-plus.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 11966] Valgrind segfaults on startup on armhf

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=11966

--- Comment #1 from andreas.kremser.ext at b-plus.com ---
Created attachment 8111
  --> https://bugs.busybox.net/attachment.cgi?id=8111&action=edit
Patch to downgrade valgrind to 3.12

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 11966] Valgrind segfaults on startup on armhf

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=11966

--- Comment #2 from andreas.kremser.ext at b-plus.com ---
Created attachment 8116
  --> https://bugs.busybox.net/attachment.cgi?id=8116&action=edit
Allow Selection of Valgrind on aarch64

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 11966] Valgrind segfaults on startup on armhf

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=11966

--- Comment #3 from andreas.kremser.ext at b-plus.com ---
Created attachment 8121
  --> https://bugs.busybox.net/attachment.cgi?id=8121&action=edit
buildroot config

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 11966] Valgrind segfaults on startup on armhf

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=11966

--- Comment #4 from Peter Seiderer <ps.report@gmx.net> ---
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?

-- 
You are receiving this mail because:
You are on the CC list for the bug.