aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/Compression.cpp
diff options
context:
space:
mode:
authorAdrian McCarthy <amccarth@google.com>2020-07-28 17:45:33 -0700
committerAdrian McCarthy <amccarth@google.com>2020-08-11 13:44:14 -0700
commit479f5bfdb02b191f03b3de1a7c3d5a5098b3fcaf (patch)
tree1dc09500b135141b4d714db71ef719abf7761a49 /llvm/lib/Support/Compression.cpp
parentdf79e18796d09f33d15974c55cca8b2b5b484e1f (diff)
downloadllvm-479f5bfdb02b191f03b3de1a7c3d5a5098b3fcaf.zip
llvm-479f5bfdb02b191f03b3de1a7c3d5a5098b3fcaf.tar.gz
llvm-479f5bfdb02b191f03b3de1a7c3d5a5098b3fcaf.tar.bz2
[LLDB] Improve PDB discovery
When loading a PE/COFF target, the associated PDB file often wasn't found. The executable module contains a path for the associated PDB file, but people often debug from a different directory than the one their build system uses. (This is especially common in post-mortem and cross platform debugging.) Suppose the COFF executable being debugged is `~/proj/foo.exe`, but it was built elsewhere and refers to `D:\remote\build\env\foobar.pdb`, LLDB wouldn't find it. With this change, if no file exists at the PDB path, LLDB will look in the executable directory for a PDB file that matches the name of the one it expected (e.g., `~/proj/foobar.pdb`). If found, the PDB is subject to the same matching criteria (GUIDs and age) as would have been used had it been in the original location. This same-directory-as-the-binary rule is commonly used by debuggers on Windows. Differential Review: https://reviews.llvm.org/D84815
Diffstat (limited to 'llvm/lib/Support/Compression.cpp')
0 files changed, 0 insertions, 0 deletions