> # valgrind --tool=memcheck --leak-check=yes --show-reachable=yes > --num-callers=20 ./test-arm-static > ==2131== HEAP SUMMARY: > ==2131== in use at exit: 0 bytes in 0 blocks > ==2131== total heap usage: 0 allocs, 0 frees, 0 bytes allocated > ==2131== > ==2131== All heap blocks were freed -- no leaks are possible > ==2131== > ==2131== For counts of detected and suppressed errors, rerun with: -v > ==2131== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
This happens because the executable is statically linked, so Memcheck fails to intercept the malloc/free calls, and so it doesn't think that the program didn't do any malloc/free calls. Memcheck won't work properly in this situation. J ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
