Bug 2214397

Summary: callgrind_control produces (strict perl) errors
Product: Red Hat Enterprise Linux 9 Reporter: Mark Wielaard <mjw>
Component: valgrindAssignee: Mark Wielaard <mjw>
valgrind sub component: system-version QA Contact: Jesus Checa <jchecahi>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: fweimer, jakub, ohudlick
Version: 9.3Keywords: Triaged
Target Milestone: rc   
Target Release: 9.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: valgrind-3.21.0-7.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2214398 (view as bug list) Environment:
Last Closed: 2023-11-07 08:30:22 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:
Bug Depends On:    
Bug Blocks: 2214398    
Deadline: 2023-07-03   

Description Mark Wielaard 2023-06-12 20:34:44 UTC 
The perl script were made to use strict; but the callgrind_control script is not correct perl strict. Causing:

$ callgrind_control --help
Global symbol "@pids" requires explicit package name (did you forget to declare "my @pids"?) at /usr/bin/callgrind_control line 35.
Global symbol "$vgdbPrefixOption" requires explicit package name (did you forget to declare "my $vgdbPrefixOption"?) at /usr/bin/callgrind_control line 36.
Global symbol "$pid" requires explicit package name (did you forget to declare "my $pid"?) at /usr/bin/callgrind_control line 39.
[...]

Upstream fixed this by rewriting the script. I like to simply remove the use strict; line to get back to the known working version. Already done in Fedora.
Comment 7 errata-xmlrpc 2023-11-07 08:30:22 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:6395