On 28/08/15 15:06, John OSullivan wrote: > I have a problem running valgrind on my embedded system, you can see the > detail below but essentially the problem is that Valgrind fails with: > FATAL: aspacem assertion failed > > The problem is caused by valgrind detecting a inode number of zero for libc > b6dae000-b6eea000 r-xp 00000000 00:00 8937 /lib/libc-2.13.so > ^^^^^ > dev & ino are always zero > > My system boots from nand and copies the file system to ram, so the file > system runs from ram, as far as I can determine when running from ram the > device and inode number are going to always be zero. > I tried a similar exercise with the Raspberry PI, if the PIs file system > reside in Ram (Volatile) then the device and inodes will always be zero, if > I put the PIs file system on the SD Card (non volatile) then I get non-zero > device and inodes for the relevant sections. > > My question is how am I going to use valgrind on a ram based file system > when device numbers are going to be zero for libc, is there a configuration > or setting that I am missing.
Surely the filesystem is still on a device, even if that device is a ramfs device? and that device should have major and minor numbers? Unfortunately unix semantics mean that you always have to have unique device numbers otherwise there is no way to tell if two identical inodes refer to the same file or not. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
