Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2124345

Summary: routine rebase of valgrind for rhel 8.9
Product: Red Hat Enterprise Linux 8 Reporter: Mark Wielaard <mjw>
Component: valgrindAssignee: Mark Wielaard <mjw>
valgrind sub component: system-version QA Contact: Jesus Checa <jchecahi>
Status: CLOSED ERRATA Docs Contact: Jacob Taylor Valdez <jvaldez>
Severity: unspecified    
Priority: unspecified CC: dsmith, fweimer, jakub, jchecahi, jvaldez, lkuprova, ohudlick, wcohen
Version: 8.8Keywords: FutureFeature, Rebase, Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.9   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: valgrind-3.21.0-2.el8 Doc Type: Enhancement
Doc Text:
.Valgrind rebased to version 3.21.0 Valgrind has been updated to version 3.21.0. Notable enhancements include: * A new `abexit` value for the `--vgdb-stop-at=_event1_,_event2_,...` option notifies the `gdbserver` utility when your program exits abnormally, such as with a non-zero exit code. * A new `--enable-debuginfod=[yes|no]` option instructs Valgrind to use the `debuginfod` servers listed in the `DEBUGINFOD_URLS` environment variable to fetch any missing DWARF debuginfo information for the program running under Valgrind. The default value for this option is `yes`. + NOTE: The `DEBUGINFOD_URLS` environment variable is not set by default. * The `vgdb` utility now supports the extended remote protocol when invoked with the `--multi` option. The GDB `run` command is supported in this mode and, as a result, you can run GDB and Valgrind from a single terminal. * You can use the `--realloc-zero-bytes-frees=[yes|no]` option to change the behavior of the `realloc()` function with a size of zero for tools that intercept the `malloc()` call. * The `memcheck` tool now performs checks for the use of the `realloc()` function with a size of zero. Use the new `--show-realloc-size-zero=[yes|no]` switch to disable this feature. * You can use the new `--history-backtrace-size=_value_` option for the `helgrind` tool to configure the number of entries to record in the stack traces of earlier accesses. * The `--cache-sim=[yes|no]` `cachegrind` option now defaults to `no` and, as a result, only instruction cache read events are gathered by default. * The source code for the `cg_annotate`, `cg_diff`, and `cg_merge` `cachegrind` utilities has been rewritten and, as a result, the utilities have more flexible command line option handling. For example, they now support the `--show-percs` and `--no-show-percs` options as well as the existing `--show-percs=yes` and `--show-percs=no` options. * The `cg_annotate` `cachegrind` utility now supports diffing (using the `--diff`, `--mod-filename`, and `--mod-funcname` options) and merging (by passing multiple data files). In addition, `cg_annotate` now provides more information at the file and function level. * A new user-request for the `DHAT` tool allows you to override the 1024 byte limit on access count histograms for blocks of memory. The following new architecture-specific instruction sets are now supported: * 64-bit ARM: ** v8.2 scalar and vector Floating-point Absolute Difference (FABD), Floating-point Absolute Compare Greater than or Equal (FACGE), Floating-point Absolute Compare Greater Than (FACGT), and Floating-point Add (FADD) instructions. ** v8.2 Floating-point (FP) compare and conditional compare instructions. ** Zero variants of v8.2 Floating-point (FP) compare instructions. * 64-bit IBM Z: ** Support for the `miscellaneous-instruction-extensions facility 3` and the `vector-enhancements facility 2`. This enables programs compiled with the `-march=arch13` or `-march=z15` options to be executed under Valgrind. * IBM Power: ** ISA 3.1 support is now complete. ** ISA 3.0 now supports the deliver a random number (darn) instruction. ** ISA 3.0 now supports the System Call Vectored (scv) instruction. ** ISA 3.0 now supports the copy, paste, and cpabort instructions.
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-14 15:32:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mark Wielaard 2022-09-05 18:35:39 UTC
Expecting v3.20.0.

Comment 10 Mark Wielaard 2023-10-13 17:16:46 UTC
* A new `abexit` value for the `--vgdb-stop-at=_event1_,_event2_,…` option launches the `gdbserver` utility when your program exits abnormally, such as with a non-zero exit code.

That should probably say "notifies" instead of "launches".

And maybe it should say that the DEBUGINFOD_URLS environment variable isn't set by default?

Apart from that this looks good. Thanks.

Comment 13 errata-xmlrpc 2023-11-14 15:32:03 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 (valgrind bug fix and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2023:6953