From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Valgrind on buildroot
Date: Fri, 05 Jun 2015 13:36:35 +0200 [thread overview]
Message-ID: <876172mloc.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <55706138.8161b40a.6051.ffffccd2SMTPIN_ADDED_BROKEN@mx.google.com> (John OSullivan's message of "Thu, 4 Jun 2015 15:30:58 +0100")
>>>>> "John" == John OSullivan <john.osullivan@cloudiumsystems.com> writes:
> Hi,
> I have been trying to get valgrind working on a buildroot 2013.05 arm board.
2013.05? Any reason you are not using 2015.05?
A quick grep in the valgrind source I see references to fixes bugs
related to this:
NEWS.old:124528 FATAL: aspacem assertion failed: segment_is_sane
NEWS.old:126722 assertion: segment_is_sane at m_aspacemgr/aspacemgr.c:1624
(Those numbers refers to issues on http://bugs.kde.org).
Testing with 2015.05 I cannot reproduce this issue (with
qemu_x86_defconfig and default external toolchain).
--
Bye, Peter Korsgaard
next parent reply other threads:[~2015-06-05 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55706138.8161b40a.6051.ffffccd2SMTPIN_ADDED_BROKEN@mx.google.com>
2015-06-05 11:36 ` Peter Korsgaard [this message]
2015-06-04 14:30 [Buildroot] Valgrind on buildroot John OSullivan
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=876172mloc.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox