Re: [Valgrind-users] The stack traces given by Memcheck on ARM are missing information

[John O'S. <joh...@cl...>]

I think I have found the issue, the libraries in /usr/lib/valgrind were 
being stripped as part of the rootfs build, excluding these from 
stripping now gives me

  valgrind --leak-check=full  --track-origins=yes --num-callers=4 /work/test
==1240== Memcheck, a memory error detector
==1240== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==1240== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==1240== Command: /work/test
==1240==
==1240== Invalid write of size 4
==1240==    at 0x8680: f (test.c:6)
==1240==    by 0x869B: main (test.c:13)
==1240==  Address 0x49b5050 is 0 bytes after a block of size 40 alloc'd
==1240==    at 0x4837774: malloc (vg_replace_malloc.c:270)
==1240==    by 0x866B: f (test.c:5)
==1240==    by 0x869B: main (test.c:13)
==1240==
==1240==
==1240== HEAP SUMMARY:
==1240==     in use at exit: 40 bytes in 1 blocks
==1240==   total heap usage: 1 allocs, 0 frees, 40 bytes allocated
==1240==
==1240== 40 bytes in 1 blocks are definitely lost in loss record 1 of 1
==1240==    at 0x4837774: malloc (vg_replace_malloc.c:270)
==1240==    by 0x866B: f (test.c:5)
==1240==    by 0x869B: main (test.c:13)
==1240==
==1240== LEAK SUMMARY:
==1240==    definitely lost: 40 bytes in 1 blocks
==1240==    indirectly lost: 0 bytes in 0 blocks

On 17/09/15 09:46, John O'Sullivan wrote:
> valgrind --leak-check=full  --track-origins=yes --num-callers=4 /work/test