Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John OSullivan <john.osullivan@cloudiumsystems.com>
To: buildroot@busybox.net
Subject: [Buildroot] Valgrind on buildroot
Date: Thu, 4 Jun 2015 15:30:58 +0100	[thread overview]
Message-ID: <00f501d09ed3$13c8d000$3b5a7000$@osullivan@cloudiumsystems.com> (raw)

Hi,

I have been trying to get valgrind working on a buildroot 2013.05 arm board.

valgrind -d -d

fails to run with 

--2993:0:aspacem  Valgrind: FATAL: aspacem assertion failed:

--2993:0:aspacem    segment_is_sane

--2993:0:aspacem    at m_aspacemgr/aspacemgr-linux.c:1477 (add_segment)

--2993:0:aspacem  Exiting now.

 

The issue is with the device node for libc

00008000-00106000 r-xp 00000000 00:00 8773       /bin/busybox

0010e000-0010f000 rw-p 000fe000 00:00 8773       /bin/busybox

0010f000-00111000 rw-p 00000000 00:00 0          [heap]

b6dae000-b6eea000 r-xp 00000000 00:00 8937       /lib/libc-2.13.so

                                ^^^^^

                                 dev & ino are always zero

 

valgrind is not expecting a zero for b6dae000-b6eea000 r-xp 00000000 00:00
8937       /lib/libc-2.13.so

 

The build options I am using are:

 

Filesystem images->cpio the root filesystem (initial RAM Filoesystem)

Filesystem images->ext2/3/4 root filesystem

(0)Size in blocks

(0)Inodes (auto calculation)

(0)Reserved blocks percentage

 

Any ideas on how to change this to non-zero so that Valgrind will read it
correctly, it works fine on rabpberrypi, but my filesystem is on the SD
Card,

Other info that might be useful follows

 

 

 

My /proc/self/maps is as follows:

--------------------------

00008000-00106000 r-xp 00000000 00:00 8773       /bin/busybox

0010e000-0010f000 rw-p 000fe000 00:00 8773       /bin/busybox

0010f000-00111000 rw-p 00000000 00:00 0          [heap]

b6dae000-b6eea000 r-xp 00000000 00:00 8937       /lib/libc-2.13.so

b6eea000-b6ef2000 ---p 0013c000 00:00 8937       /lib/libc-2.13.so

b6ef2000-b6ef4000 r--p 0013c000 00:00 8937       /lib/libc-2.13.so

b6ef4000-b6ef5000 rw-p 0013e000 00:00 8937       /lib/libc-2.13.so

b6ef5000-b6ef8000 rw-p 00000000 00:00 0 

b6ef8000-b6f66000 r-xp 00000000 00:00 8935       /lib/libm-2.13.so

b6f66000-b6f6d000 ---p 0006e000 00:00 8935       /lib/libm-2.13.so

b6f6d000-b6f6e000 r--p 0006d000 00:00 8935       /lib/libm-2.13.so

b6f6e000-b6f6f000 rw-p 0006e000 00:00 8935       /lib/libm-2.13.so

b6f6f000-b6f8f000 r-xp 00000000 00:00 8945       /lib/ld-2.13.so

b6f91000-b6f92000 rw-p 00000000 00:00 0

b6f94000-b6f95000 rw-p 00000000 00:00 0 

b6f95000-b6f96000 r-xp 00000000 00:00 0          [sigpage]

b6f96000-b6f97000 r--p 0001f000 00:00 8945       /lib/ld-2.13.so

b6f97000-b6f98000 rw-p 00020000 00:00 8945       /lib/ld-2.13.so

bee7c000-bee9d000 rw-p 00000000 00:00 0          [stack]

ffff0000-ffff1000 r-xp 00000000 00:00 0          [vectors]

----------------------------------------------

# cat /proc/cpuinfo 

processor       : 0

model name      : ARMv7 Processor rev 0 (v7l)

Features        : swp half thumb fastmult vfp edsp neon vfpv3 tls

vfpd32

CPU implementer : 0x41

CPU architecture: 7

CPU variant     : 0x3

CPU part        : 0xc09

CPU revision    : 0

 

processor       : 1

model name      : ARMv7 Processor rev 0 (v7l)

Features        : swp half thumb fastmult vfp edsp neon vfpv3 tls

vfpd32

CPU implementer : 0x41

CPU architecture: 7

CPU variant     : 0x3

CPU part        : 0xc09

CPU revision    : 0

 

Hardware        : Xilinx Zynq Platform

Revision        : 0000

Serial          : 0000000000000000

 

Regards

John

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150604/cc626682/attachment.html>

             reply	other threads:[~2015-06-04 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 14:30 John OSullivan [this message]
     [not found] <55706138.8161b40a.6051.ffffccd2SMTPIN_ADDED_BROKEN@mx.google.com>
2015-06-05 11:36 ` [Buildroot] Valgrind on buildroot Peter Korsgaard

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='00f501d09ed3$13c8d000$3b5a7000$@osullivan@cloudiumsystems.com' \
    --to=john.osullivan@cloudiumsystems.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