Red Hat Bugzilla – Bug 651152
[LTC 5.7 FEAT] Valgrind System z support - installer part
Last modified: 2011-05-13 08:33:17 EDT
1. Feature Overview:
Feature Id: 
a. Name of Feature: [LTC 5.7 FEAT] Valgrind System z support - installer part
b. Feature Description
This feature requests to add Valgrind package support to Linux on System z installations. The
package upgrade (3.6.0) and patch on top to have the System z back end is requested and tracked in a
2. Feature Details:
Sponsor: LTC zSeries BOE
Architectures: zSeries - 64 native,
Arch Specificity: both
Affects Kernel Modules: No
Delivery Mechanism: LDP Deliverable
Request Type: Code Development Support from Distributor
d. Upstream Acceptance: In Progress
Sponsor Priority P1
f. Severity: ship issue
IBM Confidential: No
Code Contribution: 3rd party code
g. Component Version Target: ---
h. Code Development Support from Distributor
3. Business Case
Valgrind has proven to be a valuable tool debugging user-space memory management problem on x86 and
PPC platforms. Several customers have requested to have this tool on System z as well. Besides the
capabilities to debug memory problems other plugins (cachegrind) enable us to analyze the cache
access patterns of applications which turned out to be a key issue in order to get the best
performance on z10 machines.
4. Primary contact at Red Hat:
John Jarvis, email@example.com
5. Primary contacts at Partner:
Project Management Contact:
Hans-Georg Markgraf, firstname.lastname@example.org
Gonzalo Muelas Serrano, email@example.com
What possible thing could be required from anaconda to support valgrind?
------- Comment From firstname.lastname@example.org 2010-12-17 03:13 EDT-------
The installer part of the Valgrind feature requests to add Valgrind to the list of packages in installer to have Valgrind available as installable option..
That is controlled by comps.
Valgrind is not available on s390x because it's not built for 390x.
Reassigning to valgrind component.
That is already covered in bug 651163. Once that is done, there are no other changes needed.
*** This bug has been marked as a duplicate of bug 651163 ***