Relative DWO files are normally found at some/path/to/file.dwo.
Currently lldb will find the file by adding that path to the
binary's location and to any debug search paths that are set.
This patch adds a fallback on top of that where lldb will look
for just the filename (file.dwo) in those same places.
So if you had flattened a build directory before distribution,
you could still get symbols. Or perhaps you send out a DWO file
on demand, and don't want people to have to recreate the directory
layout.
For example if you were built:
program
obj/program.dwo
And changed to:
program
program.dwo
<binary dir>/obj/program.dwo is not found.
<binary dir>/program.dwo is.
If the layout was changed to:
program
mydebuginfo/progam.dwo
And we had a debug search path of <binary dir>/mydebuginfo:
- <binary dir>/mydebuginfo/obj/program.dwo is not found.
- <binary dir>/mydebuginfo/program.dwo is found.
clang-format not found in user’s local PATH; not linting file.