RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1473725 - Rebase Valgrind for 7.5
Summary: Rebase Valgrind for 7.5
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: valgrind
Version: 7.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Mark Wielaard
QA Contact: Miloš Prchlík
Vladimír Slávik
Depends On:
Blocks: 1471969
TreeView+ depends on / blocked
Reported: 2017-07-21 13:50 UTC by mbenitez
Modified: 2018-04-10 13:14 UTC (History)
9 users (show)

Fixed In Version: valgrind-3.13.0-9.el7
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
_valgrind_ rebased to version 3.13.0 The _valgrind_ package has been upgraded to version 3.13.0, which provides a number of bug fixes and enhancements over the previous version. Notable changes are: * *Valgrind* has been extended in several ways to run large programs. The amount of memory usable by *Valgrind* has been increased to 128 GB. As a consequence, the *Memcheck* tool supports running applications that allocate up to approximately 60 GB. Additionally, *Valgrind* can now load executable files up to 1200 MB in size. * The tools *Memcheck*, *Helgrind*, and *Massif* can now use a new execution tree (xtree) representation to report heap consumption of the analyzed applications. * The symbol demangler has been updated to support the C++11 standard and the Rust programming language. * Failures with long blocks of code using AVX2 instructions on the Intel and AMD 64-bit architecture have been fixed. * The 64-bit `timebase` register of the PowerPC architecture is no longer modeled by *Valgrind* as only 32-bit. * Support for the IBM Power Systems architecture has been extended to include the ISA 3.0B specification. * An alternative implementation of Load-Linked and Store-Conditional instructions for the 64-bit ARM architecture has been added. The alternative implementation is enabled automatically when required. To enable it manually, use the `--sim-hints=fallback-llsc` option.
Clone Of:
: 1496376 (view as bug list)
Last Closed: 2018-04-10 13:14:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0773 0 None None None 2018-04-10 13:14:45 UTC

Description mbenitez 2017-07-21 13:50:09 UTC

Comment 2 Mark Wielaard 2017-08-07 14:03:02 UTC
This would update valgrind from 3.12.x to 3.13.x.
3.13 was released upstream last June.

Comment 7 Miloš Prchlík 2018-01-05 13:55:05 UTC
Verified for build valgrind-3.13.0-10.el7.

Comment 10 errata-xmlrpc 2018-04-10 13:14:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.