On Wed, Sep 2, 2009 at 10:11 AM, Jarkko Palviainen<jarkko.palviai...@gmail.com> wrote: > > Happens to me as well. I'm not sure what's the problem with the binary > package, but rebuilding it seems to help. This is what I get with the > rebuilt valgrind_3.4.1-1ubuntu1_i386.deb: > > $ valgrind echo foo > ==25041== Memcheck, a memory error detector. > ==25041== Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et al. > ==25041== Using LibVEX rev 1884, a library for dynamic binary translation. > ==25041== Copyright (C) 2004-2008, and GNU GPL'd, by OpenWorks LLP. > ==25041== Using valgrind-3.4.1-Debian, a dynamic binary instrumentation > framework. > ==25041== Copyright (C) 2000-2008, and GNU GPL'd, by Julian Seward et al. > ==25041== For more details, rerun with: -v > ==25041== > foo > ==25041== > ==25041== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 1) > ==25041== malloc/free: in use at exit: 0 bytes in 0 blocks. > ==25041== malloc/free: 1,387 allocs, 1,387 frees, 64,390 bytes allocated. > ==25041== For counts of detected errors, rerun with: -v > ==25041== All heap blocks were freed -- no leaks are possible. > >
Hi Jarkko, Thank you for your response. I can confirm that rebuilding the same version of the valgrind package solves the problem for me as well. Should anything else be done to triage this? Could other packages be lurking in the repository that need to be rebuilt? Regards, Mike -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
