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 2208571 - Fix valgrind-monitor python script location
Summary: Fix valgrind-monitor python script location
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2023-06-12
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: valgrind
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Mark Wielaard
QA Contact: Jesus Checa
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-19 15:15 UTC by Mark Wielaard
Modified: 2023-11-07 09:34 UTC (History)
5 users (show)

Fixed In Version: valgrind-3.21.0-3.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2208574 (view as bug list)
Environment:
Last Closed: 2023-11-07 08:30:22 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-157748 0 None None None 2023-05-19 15:17:35 UTC
Red Hat Product Errata RHBA-2023:6395 0 None None None 2023-11-07 08:30:37 UTC

Description Mark Wielaard 2023-05-19 15:15:16 UTC 
One of the new features for valgrind 3.21.0 (see bug #2124346) are the gdb python scripts. But currently when you use these, gdb will warn a lot:

warning: File "/usr/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
	add-auto-load-safe-path /usr/libexec/valgrind/valgrind-monitor.py
line to your configuration file "/home/mark/.config/gdb/gdbinit".
To completely disable this security protection add
	set auto-load safe-path /
line to your configuration file "/home/mark/.config/gdb/gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
	info "(gdb)Auto-loading safe path"

We have a patch upstream and in Fedora to move the scripts under /usr/gdb/auto-load so they are loaded automatically. This really improves the usability.
Comment 1 Jesus Checa 2023-05-30 11:27:15 UTC 
Tested with valgrind-3.21.0-3.el9. The warnings are not showing up anymore.

Output from valgrind-3.21.0-2.el9:
-----
0x0000000004017cd0 in _start () from /lib/ld-linux-aarch64.so.1
Breakpoint 1 at 0x400694: file something.c, line 10.
warning: File "/usr/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
	add-auto-load-safe-path /usr/libexec/valgrind/valgrind-monitor.py
line to your configuration file "/root/.gdbinit".
To completely disable this security protection add
	set auto-load safe-path /
line to your configuration file "/root/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
	info "(gdb)Auto-loading safe path"

Breakpoint 1, main (argc=1, argv=0x1ffefff578) at something.c:10
----

Output from valgrind-3.21.0-3.el9:
----
0x0000000004016110 in _start () from /lib/ld-linux-aarch64.so.1
Breakpoint 1 at 0x400644: file something.c, line 10.

Breakpoint 1, main (argc=1, argv=0x1fff00dfc8) at something.c:10
----
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
Note You need to log in before you can comment on or make changes to this bug.