DebugInfo: Provide option for explicitly specifying the name of the DWP file
authorDavid Blaikie <dblaikie@gmail.com>
Sun, 30 Jul 2017 01:34:08 +0000 (01:34 +0000)
committerDavid Blaikie <dblaikie@gmail.com>
Sun, 30 Jul 2017 01:34:08 +0000 (01:34 +0000)
commite5adb68e044da6733e9ebba7aea913c1ca9618dd
tree6adf83bda66ffc3c19525d26104077ef61275d65
parent67b0e589d02e4e17815ab6f2e0f72b4b8190b41b
DebugInfo: Provide option for explicitly specifying the name of the DWP file

If you've archived the DWP file somewhere it's probably useful to be
able to just tell llvm-symbolizer where it is when you're symbolizing
stack traces from the binary.

This only provides a mechanism for specifying a single DWP file, good if
you're symbolizing a program with a single DWP file, but it's likely if
the program is dynamically linked that you might have a DWP for each
dynamic library - in which case this feature won't help (at least as
it's surfaced in llvm-symbolizer for now) - in theory it could be
extended to specify a collection of DWP files that could all be
consulted for split CU hash resolution.

llvm-svn: 309498
llvm/include/llvm/DebugInfo/DWARF/DWARFContext.h
llvm/include/llvm/DebugInfo/Symbolize/Symbolize.h
llvm/lib/DebugInfo/DWARF/DWARFContext.cpp
llvm/lib/DebugInfo/Symbolize/Symbolize.cpp
llvm/test/DebugInfo/llvm-symbolizer.test
llvm/tools/llvm-symbolizer/llvm-symbolizer.cpp