Skip to contentSkip to conversation

New: Valgrind segfaults on startup on armhf

Buildroot bugzilla at busybox.net 1 participant 6 messages Jun 18, 2019 – Jun 15, 2024

lore
Share & tools
lore
#0 lore raw

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.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#4 lore raw

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

In reply to bugzilla at busybox.net

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

--- Comment #4 from Peter Seiderer <[email protected]> --- 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?

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#5 lore raw

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

In reply to bugzilla at busybox.net

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

Yann E. MORIN <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected]
         Resolution|---                         |MOVED
             Status|NEW                         |RESOLVED

--- Comment #5 from Yann E. MORIN <[email protected]> --- 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!

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot