Ubuntu
valgrind package

  1. Bug #881236
  2. Comment #2

Comment 2 for bug 881236

Revision history for this message
Loïc Minier (lool) wrote : Re: valgrind on amd64 no longer works with 32-bit binaries

Works for me with 1:3.6.1-6ubuntu1 from Ubuntu precise:
gcc -m64 -o hello hello.c
valgrind ./hello
==20954== Memcheck, a memory error detector
==20954== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==20954== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info
==20954== Command: ./hello
==20954==
hello.
==20954==
==20954== HEAP SUMMARY:
==20954== in use at exit: 0 bytes in 0 blocks
==20954== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==20954==
==20954== All heap blocks were freed -- no leaks are possible
==20954==
==20954== For counts of detected and suppressed errors, rerun with: -v
==20954== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)

I don't see which packaging change could have fixed this, so this might be a difference in our installed packages; one thing I would have thought would help is installing libc6-dbg:i386, but it turns out it's *not* installed on my system.

However my libc6-dbg:amd64 package does ship /usr/lib/debug/lib32/libc-2.13.so and others.