Bug 294761

Summary: valgrind.i386 doesn't exist for x86_64
Product: [Fedora] Fedora Reporter: John Haxby <jch>
Component: mashAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Bill Nottingham <notting>
Severity: medium Docs Contact:
Priority: low    
Version: 7CC: dcantrell, jakub, katzj, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-18 15:49:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Haxby 2007-09-18 14:19:31 UTC
Description of problem:

Previously, in Fedora Core 6, both valgrind.i386 and valgrind.x86_64 were
available, in Fedora 7, only valgrind.x86_64 is available.


Version-Release number of selected component (if applicable): 3.2.3-5.fc7


How reproducible:


Steps to Reproduce:
1. yum install valgrind (note only x86_64 version offered)
2. valgrind <32-bit program>

  
Actual results:

valgrind complains about a missing tool (memcheck)

Expected results:

valgrind runs as normal


Additional info:

I took the valgrind.i386 from the Fedora 7 i386 updates repo and installed it
with "rpm -Uvh" and everything works now.  This is a step backwards from Fedora
Core 6 though: in that release I had a working 32 bit valgrind without having to
do anything at all.

Comment 1 Jakub Jelinek 2007-09-18 14:30:24 UTC
That's an Fedora release engineering issue, the packages are built correctly.

Comment 2 Bill Nottingham 2007-09-18 15:08:52 UTC
valgrind for x86_64 does not work in i386?

Comment 3 Jakub Jelinek 2007-09-18 15:19:21 UTC
No.  The /usr/bin/valgrind program is just a tiny wrapper which can dispatch
to the right valgrind backend (32-bit or 64-bit), but if you want to trace
both kinds of programs, you need both kinds of backends installed.  Which means
both valgrind.x86_64 and valgrind.i386 should be installed on x86_64,
on ppc with 64-bit kernel if you want to trace both, you also need both
valgrind.ppc and valgrind.ppc64, etc.

Comment 4 Bill Nottingham 2007-09-18 15:38:23 UTC
Whee, so valgrind is in a completely different category from gdb, strace, etc.,
in that you need both.

Comment 5 Bill Nottingham 2007-09-18 15:49:59 UTC
Added in mash-0.2.5.