[Lldb-commits] [PATCH] D40539: Allow using the object file name for debug symbol resolution
Stephane Sezer via Phabricator via lldb-commits
lldb-commits at lists.llvm.org
Tue Nov 28 10:25:54 PST 2017
sas added a comment.
In https://reviews.llvm.org/D40539#937900, @clayborg wrote:
> In https://reviews.llvm.org/D40539#937854, @sas wrote:
> > Basically, if you have a `.debug` directory in the same directory where the original object file is, you can have debug symbols there. For instance, you can have:
> > /my/project/myElf.exe
> > /my/project/.debug/myElf.exe
> > with the first file being a standard stripped elf file, and the second one being the associated debug symbols.
> Do adding a FileSpec that contains just the basename will cause us to look for this file in the same directory as the original ELF file in the .debug folder?
> Does this occur elsewhere? Why not just construct the correct path in FileSpec to begin with?
It occurs in some other class where we try to locate the debug symbols for a given object file. There, we construct the list of paths to look for because we use multiple sources to get the paths. We use the setting I mentioned earlier, the `.debug` folder, and some order path scheme with `.build-id` folders.
More information about the lldb-commits