Skip to contentSkip to conversation

Question about filesystem and Valgrind

Buildroot John OSullivan 2 participants 3 messages May 12, 2015 – May 13, 2015

lore
Share & tools
lore
#0 lore raw

Hi,

I am not sure if this is a buildroot issue, but buildroot 2015.02 is the tool I use to build my filesystem for an Arm based embedded board that I am using.

I am using libc (rather than uclibc) and when I run Valgrind on my target it fails with.

Quoted 3 lines

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

--2993:0:aspacem segment_is_sane

The issue it is identifying is with the filesystem:

If I cat /proc/self/maps I get

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

the entry for /lib/libc-2.13.so should not have 00 for the device number.

I am not sure where to start with this, is this something I can configure via build root or is it a kernel config issue. Any clues on where to start would be greatly appreciated.

Regards

John

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

#1 lore raw
Quoted 15 lines · John OSullivan

Hi,

I am not sure if this is a buildroot issue, but buildroot 2015.02 is the tool I use to build my filesystem for an Arm based embedded board that I am using.

I am using libc (rather than uclibc) and when I run Valgrind on my target it fails with.

Quoted 2 lines

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

The issue it is identifying is with the filesystem:

If I cat /proc/self/maps I get

Quoted 8 lines
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

the entry for /lib/libc-2.13.so should not have 00 for the device number.

0 generally means memory. Are you running from a ramdisk with execute-in-place?

#2 lore raw

Hi Mark,

Thanks for taking the time to reply, my system boots from nand and then copies the rootfs into ram, the code is run from ram. As indicated when I look at /proc/self/maps for libc I see a zero device id. I do not see this on my Ubuntu machine or on my raspberypi.
Do you think the zero device ID is because my filesystem is in Ram? Has buildroot configs any control over these Ids? I assume lots of people run valgrind on embedded systems with similar arrangements and valgrind is expecting a non zero id for libc.

Regards
John

-----Original Message-----
From: Mark Mason [mailto:mason+buildroot at postdiluvian.org]
Sent: 12 May 2015 18:51
To: John OSullivan
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] Question about filesystem and Valgrind

Quoted 4 lines · John OSullivan

Hi,

I am not sure if this is a buildroot issue, but buildroot 2015.02 is the tool I use to build my filesystem for an Arm based embedded board that

I am using.

Quoted 11 lines

I am using libc (rather than uclibc) and when I run Valgrind on my target it fails with.

Quoted 2 lines

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

The issue it is identifying is with the filesystem:

If I cat /proc/self/maps I get

Quoted 8 lines
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

the entry for /lib/libc-2.13.so should not have 00 for the device number.

0 generally means memory. Are you running from a ramdisk with execute-in-place?