mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2024-11-23 22:00:10 +00:00
a723694321
Fixes #28667 There's a bunch of ways to end up building split DWARF where the DWO file is not next to the program file. On top of that you may distribute the program in various ways, move files about, switch machines, flatten the directories, etc. This change adds a few more strategies to find DWO files: * Appending the DW_AT_COMP_DIR and DWO name to all the debug search paths. * Appending the same to the binary's dir. * Appending the DWO name (e.g. a/b/foo.dwo) to all the debug search paths. * Appending the DWO name to the binary's location. * Appending the DWO filename (e.g. foo.dwo) to the debug search paths. * Appending the DWO filename to the binary's location. They are applied in that order and some will be skipped if the DW_AT_COMP_DIR is relative or absolute, same for the DWO name (though that seems to always be relative). This uses the setting target.debug-file-search-paths, which is used for DWP files already. The added tests likely do not cover every part of the strategies listed, it's a best effort. Reviewed By: clayborg Differential Revision: https://reviews.llvm.org/D157609 |
||
|---|---|---|
| .. | ||
| API | ||
| Shell | ||
| Unit | ||
| CMakeLists.txt | ||
| lit.cfg.py | ||
| lit.site.cfg.py.in | ||