Same problem here. I got the valgrind working with some real stupid hack but not sure what it breaks. Here are the steps:
1. Move from /usr/lib/debug/ the following directories to the following places:
usr/bin/ -> usr/bintmp/
usr/lib/ -> usr/libtmp/
usr/sbin/ -> usr/sbintmp/
sbin/ -> sbintmp/
2. Unpack the .deb:
sudo dpkg --unpack /var/cache/apt/archives/libc6-dbg_2.13-20ubuntu5.1_i386.deb
With this the debug system is replaced with 32bit versions of everything and I am not sure if the valgrind can actually be used for 64bit programs after this. This is most probably not the best way to fix this so still waiting for the correction for this bug.
Same problem here. I got the valgrind working with some real stupid hack but not sure what it breaks. Here are the steps:
1. Move from /usr/lib/debug/ the following directories to the following places:
usr/bin/ -> usr/bintmp/
usr/lib/ -> usr/libtmp/
usr/sbin/ -> usr/sbintmp/
sbin/ -> sbintmp/
2. Unpack the .deb: apt/archives/ libc6-dbg_ 2.13-20ubuntu5. 1_i386. deb
sudo dpkg --unpack /var/cache/
With this the debug system is replaced with 32bit versions of everything and I am not sure if the valgrind can actually be used for 64bit programs after this. This is most probably not the best way to fix this so still waiting for the correction for this bug.
valgrind- 3.6.1-Debian
Ubuntu 11.10 64bit 3.0.0-17-generic