2012/3/15 Julian Seward <[email protected]>
> Sounds like some kind of installation problem. Does
> valgrind /bin/ls
> work?
Appears to:
==3345== Memcheck, a memory error detector.
==3345== Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et al.
==3345== Using LibVEX rev 1884, a library for dynamic binary translation.
==3345== Copyright (C) 2004-2008, and GNU GPL'd, by OpenWorks LLP.
==3345== Using valgrind-3.4.1-Debian, a dynamic binary instrumentation
framework.
==3345== Copyright (C) 2000-2008, and GNU GPL'd, by Julian Seward et al.
==3345== For more details, rerun with: -v
==3345==
Desktop examples.desktop Pictures Templates
Documents Music Public Videos
==3345==
==3345== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 23 from 1)
==3345== malloc/free: in use at exit: 12,978 bytes in 14 blocks.
==3345== malloc/free: 1,450 allocs, 1,436 frees, 85,334 bytes allocated.
==3345== For counts of detected errors, rerun with: -v
==3345== searching for pointers to 14 not-freed blocks.
==3345== checked 98,556 bytes.
==3345==
==3345== LEAK SUMMARY:
==3345== definitely lost: 0 bytes in 0 blocks.
==3345== possibly lost: 0 bytes in 0 blocks.
==3345== still reachable: 12,978 bytes in 14 blocks.
==3345== suppressed: 0 bytes in 0 blocks.
==3345== Rerun with --leak-check=full to see details of leaked memory.
Thanks!
Ian
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
