https://bugs.kde.org/show_bug.cgi?id=387773
Bug ID: 387773
Summary: Files in .gnu_debugaltlink should be resolved relative
to .debug file, not symlink.
Product: valgrind
Version: 3.14 SVN
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: m...@klomp.org
Target Milestone: ---
Created attachment 109296
--> https://bugs.kde.org/attachment.cgi?id=109296&action=edit
Fix gnu debug alt file resolving.
In some situations (Fedora 27) the .debug file is available through a build-id
symlink, but the debug alt file isn't (which arguably isn't ideal, and probably
should be fixed). In such cases resolving the debug alt file from the relative
path in the .gnu_debugaltlink should be done against the actual .debug file,
not against the (build-id) symlink that pointed to the .debug file.
This causes issues like:
$ valgrind -q /usr/libexec/pcp/bin/telnet-probe
--17775-- WARNING: Serious error when reading debug info
--17775-- When reading debug info from /usr/libexec/pcp/bin/telnet-probe:
--17775-- get_Form_contents: DW_FORM_GNU_strp_alt used, but no alternate
.debug_str
This is caused because the relative debug alt file path is resolved against the
build-id symlink file, instead of against the actual .debug file.
/usr/lib/debug/.build-id/87/1a7e7175751df1a2017ef448e5ebf390270c6f.debug ->
../../../../../usr/lib/debug/usr/libexec/pcp/bin/telnet-probe-3.12.1-3.fc27.x86_64.debug
The attached patch fixes this by making sure that the file against which any
relative paths are resolved isn't a symlink.
--
You are receiving this mail because:
You are watching all bug changes.
