https://bugs.kde.org/show_bug.cgi?id=470121
Bug ID: 470121
Summary: Can't run callgrind_control with valgrind 3.21.0
because of perl errors
Classification: Developer tools
Product: valgrind
Version: 3.21.0
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: callgrind
Assignee: josef.weidendor...@gmx.de
Reporter: romain.geiss...@amadeus.com
Target Milestone: ---
Created attachment 159185
--> https://bugs.kde.org/attachment.cgi?id=159185&action=edit
Patch workarounding the issue (ie remove "use strict;")
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. Just run `callgrind_control --help` with valgrind 3.21, you will see it
cannot run because of some perl errors. Errors are of two types:
- Global symbol "$c" requires explicit package name at ./callgrind_control line
502.
- Bareword "getCallgrindPids" not allowed while "strict subs" in use at
./callgrind_control line 220.
OBSERVED RESULT
Perl errors.
EXPECTED RESULT
No perl errors.
SOFTWARE/OS VERSIONS
Tried on SLES 12 and RHEL 9.
ADDITIONAL INFORMATION
I add this this bug report a git commit which workarounds (ie remove "use
strict;", not fix the actual errors) this issue. I hardly know anything about
perl ;) A better long term fix would be to actually fix these perl errors.
--
You are receiving this mail because:
You are watching all bug changes.
