From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11966] New: Valgrind segfaults on startup on armhf
Date: Tue, 18 Jun 2019 14:34:25 +0000 [thread overview]
Message-ID: <bug-11966-163@https.bugs.busybox.net/> (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.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-06-18 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 14:34 bugzilla at busybox.net [this message]
2019-06-18 14:36 ` [Buildroot] [Bug 11966] Valgrind segfaults on startup on armhf bugzilla at busybox.net
2019-06-18 14:37 ` bugzilla at busybox.net
2019-06-18 14:39 ` bugzilla at busybox.net
2019-07-05 21:35 ` bugzilla at busybox.net
2024-06-15 14:49 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-11966-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.