https://bugs.kde.org/show_bug.cgi?id=469768
Bug ID: 469768
Summary: Make it possible to install gdb scripts in a different
location
Classification: Developer tools
Product: valgrind
Version: 3.20.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: m...@klomp.org
CC: ahajk...@redhat.com
Target Milestone: ---
Created attachment 158950
--> https://bugs.kde.org/attachment.cgi?id=158950&action=edit
Add --with-gdbscripts-dir=PATH configure option
Add --with-gdbscripts-dir=PATH configure option
Currently the gdb valgrind scripts are installed under VG_LIBDIR
which is normally pkglibexecdir which is likely not in the default
gdb safe-path (a list of directories from which it is safe to
auto-load files). So users will have to add the directory to their
.gdbinit file.
This patch adds a --with-gdbscripts-dir=PATH configure option that
sets VG_GDBSCRIPTS_DIR to the given PATH (${libexecdir}/valgrind if
not given).
Use VG_GDBSCRIPTS_DIR as gdbscriptsdir to install the valgrind-monitor
python files and pass it with CPPFLAGS when building vg_preloaded.c
and vgdb.c to use instead of VG_LIBDIR.
--
You are receiving this mail because:
You are watching all bug changes.
