Bug 2214398 - callgrind_control produces (strict perl) errors
Summary: callgrind_control produces (strict perl) errors
Keywords:
Status: VERIFIED
Alias: None
Deadline: 2023-07-03
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: valgrind
Version: 8.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.9
Assignee: Mark Wielaard
QA Contact: Jesus Checa
URL:
Whiteboard:
Depends On: 2214397
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-12 20:36 UTC by Mark Wielaard
Modified: 2023-06-27 07:47 UTC (History)
4 users (show)

Fixed In Version: valgrind-3.21.0-7.el8
Doc Type: No Doc Update
Doc Text:
Clone Of: 2214397
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 470121 0 NOR RESOLVED Can't run callgrind_control with valgrind 3.21.0 because of perl errors 2023-06-12 20:36:53 UTC
Red Hat Issue Tracker RHELPLAN-159665 0 None None None 2023-06-12 20:38:23 UTC

Description Mark Wielaard 2023-06-12 20:36:53 UTC
+++ This bug was initially created as a clone of Bug #2214397 +++

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.


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