https://sourceware.org/bugzilla/show_bug.cgi?id=23842
Joe Burzinski <tridacnid at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tridacnid at gmail dot com
--- Comment #1 from Joe Burzinski <tridacnid at gmail dot com> ---
I have run into this same behavior and found it frustrating so I'm putting
together a small patch to change dwp to first use the relative path as it used
to and then construct an absolute path using DW_AT_comp_dir as a prefix and try
that second. I'm looking for some guidance regarding a couple things:
1. Maintaining backwards compatibility.
2. Silencing "error: cannot open a.dwo: No such file or directory" until we've
determined we also can't find a.dwo in the compile location.
3. Writing tests for this. I see two bash scripts that can be run but I'm not
sure I follow what the C++ files named dwp_test_* are doing.
As far as item 1 is concerned, I have tried to maintain backwards compatibility
by first checking relative path (what dwp used to do) and then falling back to
using the location specified by DW_AT_comp_dir to create an absolute path and
attempt to open the file at that location instead. Unfortunately, this causes
item 2 to be a problem. For the basic test case provided by Mitchell and my own
use cases dwp will give an error message for most, if not all, .dwo files that
it initially cannot find by searching the relative path.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
