Ooops. Sorry (and thanks!) My mistake: I used a hacked valgrind version that intercepted custom malloc in bash...
--kcc On Wed, Oct 1, 2008 at 3:41 PM, Andreas Bernauer <[EMAIL PROTECTED]> wrote: > Konstantin Serebryany wrote: >> Hi valgrind-users, >> >> I wonder of someone has seen this failure: >> $ valgrind bash >> ... >> malloc: ../bash/variables.c:484: assertion botched >> free: called with unallocated block argument >> > > No, I get > $ valgrind bash > ==5866== Memcheck, a memory error detector. > ==5866== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. > ==5866== Using LibVEX rev 1854, a library for dynamic binary translation. > ==5866== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. > ==5866== Using valgrind-3.3.1-Debian, a dynamic binary instrumentation > framework. > ==5866== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. > ==5866== For more details, rerun with: -v > ==5866== > ==5867== > ==5867== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 23 from 1) > ==5867== malloc/free: in use at exit: 0 bytes in 0 blocks. > ==5867== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. > ==5867== For counts of detected errors, rerun with: -v > ==5867== All heap blocks were freed -- no leaks are possible. > > [... last error summary repeated several times ... ] > > ==5892== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 23 from 1) > ==5892== malloc/free: in use at exit: 0 bytes in 0 blocks. > ==5892== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. > ==5892== For counts of detected errors, rerun with: -v > ==5892== All heap blocks were freed -- no leaks are possible. > $ exit > exit > ==5866== > ==5866== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 23 from 1) > ==5866== malloc/free: in use at exit: 0 bytes in 0 blocks. > ==5866== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. > ==5866== For counts of detected errors, rerun with: -v > ==5866== All heap blocks were freed -- no leaks are possible. > $ valgrind --version > valgrind-3.3.1-Debian > > Maybe some program you start in your profiles, rc files causes the > error? Try 'valgrind bash --noprofile --norc'. > > Cheers, > > Andreas. > > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
