Bug 174582

Summary: Please update to 3.1.0
Product: [Fedora] Fedora Reporter: Neal Becker <ndbecker2>
Component: valgrindAssignee: Jakub Jelinek <jakub>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: dwmw2
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://www.valgrind.org/
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-01-16 10:39:24 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 Neal Becker 2005-11-30 13:14:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.2 (like Gecko)

Description of problem:
Release 3.1.0 (25 November 2005) 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
 3.1.0 is a feature release with a number of significant improvements: 
 AMD64 support is much improved, PPC32 support is good enough to be 
 usable, and the handling of memory management and address space is 
 much more robust.  In detail: 
  
 - AMD64 support is much improved.  The 64-bit vs. 32-bit issues in 
   3.0.X have been resolved, and it should "just work" now in all 
   cases.  On AMD64 machines both 64-bit and 32-bit versions of 
   Valgrind are built.  The right version will be invoked 
   automatically, even when using --trace-children and mixing execution 
   between 64-bit and 32-bit executables.  Also, many more instructions 
   are supported. 
  
 - PPC32 support is now good enough to be usable.  It should work with 
   all tools, but please let us know if you have problems.  Three 
   classes of CPUs are supported: integer only (no FP, no Altivec), 
   which covers embedded PPC uses, integer and FP but no Altivec 
   (G3-ish), and CPUs capable of Altivec too (G4, G5). 
[...] 

Version-Release number of selected component (if applicable):
valgrind-2.4.0-2

How reproducible:
Always

Steps to Reproduce:
1.N/A  
2.  
3.  
    

Additional info:

Comment 1 Jakub Jelinek 2005-12-12 23:37:56 UTC
*** Bug 175577 has been marked as a duplicate of this bug. ***

Comment 2 Jakub Jelinek 2006-01-16 10:39:24 UTC
valgrind-3.1.0-1 together with valgrind-callgrind-0.10.1-1 should show up in
tomorrow's rawhide.