checking for 32 bit build support... yes
You can also use --enable-only64bit or --enable-only32bit if you only care about a specific platform.
2. Adding "-d" to valgrind will spew out a bunch of debug information, including which tool it's launching. Something like this:
--4603:1:launcher no client specified, defaulting platform to 'amd64-linux'
--4603:1:launcher launching /usr/local/lib/valgrind/memcheck-amd64-linux
"valgrind --verbose" can also be useful, of course.
3. Archive of valgrind users mailing list is here:
4. If you see this error when valgrind'ing a 32-bit application:
valgrind: Fatal error at startup: a function redirection
valgrind: which is mandatory for this platform-tool combination
valgrind: cannot be set up. Details of the redirection are:
valgrind: A must-be-redirected function
valgrind: whose name matches the pattern: strlen
valgrind: in an object with soname matching: ld-linux.so.2
valgrind: was not found whilst processing
valgrind: symbols from the object with soname: ld-linux.so.2
valgrind: Possible fixes: (1, short term): install glibc's debuginfo
valgrind: package on this machine. (2, longer term): ask the packagers
valgrind: for your Linux distribution to please in future ship a non-
valgrind: stripped ld.so (or whatever the dynamic linker .so is called)
valgrind: that exports the above-named function using the standard
valgrind: calling conventions for this platform. The package you need
valgrind: to install for fix (1) is called
valgrind: On Debian, Ubuntu: libc6-dbg
valgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo
valgrind: Cannot continue -- exiting now. Sorry.
You most likely need the 32-bit libc-dbg package. On Debian based systems this should fix it:
sudo apt-get install libc6-dbg:i386