Red Hat Bugzilla – Bug 179472
64-bit valgrind cannot debug 32-bit binaries
Last modified: 2007-11-30 17:11:22 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8) Gecko/20060126 Fedora/1.5-5 Firefox/1.5
Description of problem:
64-bit valgrind says (on x86_64):
valgrind: failed to start tool 'memcheck' for platform 'x86-linux': No such file or directory
.. on attempt to debug (32-bit) openoffice.
Installing the 32-bit valgrind in parallel does not help matters, it puts x86 memcheck in lib/x86-linux, and the 64-bit binary looks for it only in lib64/x86-linux, and doesn't find it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install 64-bit valgrind
2. Try to debug openoffice
Do you have 32-bit valgrind really installed or are you just guessing?
lrwxrwxrwx 1 root root 28 Jan 10 05:43
/usr/lib64/valgrind/x86-linux -> ../../lib/valgrind/x86-linux
... that link?
Right. I suppose it would work, if I hadn't erased this exact link yesterday
while playing with suppression files (and then completely forgotten all about
that, hence this bug).
I'm sorry, I just see a dead link, and can't resist erasing it - it has this
awful red color that seems to indicate something's wrong.
Although this doesn't make sense to me.
- Why do I need to have a 32-bit valgrind installed to debug 32-bit applications?
- Why is a package shipping a dead link to a file it doesn't own.
Something's not right about both of those things. In fact, I've though about
having a script to hunt down and delete all dead links on my system, but I see
now that this might backfire.