aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Analysis/ValueTracking.cpp
diff options
context:
space:
mode:
authorFred Riss <friss@apple.com>2020-07-17 17:59:15 -0700
committerFred Riss <friss@apple.com>2020-07-24 09:19:17 -0700
commit22c16360dd00230987fee5f6f3c57f8071144cc1 (patch)
tree9101d945bf9fc0eead657df4473cd5850117ffbf /llvm/lib/Analysis/ValueTracking.cpp
parent5934df0c9abe94fc450fbcf0ceca21cf838840e9 (diff)
downloadllvm-22c16360dd00230987fee5f6f3c57f8071144cc1.zip
llvm-22c16360dd00230987fee5f6f3c57f8071144cc1.tar.gz
llvm-22c16360dd00230987fee5f6f3c57f8071144cc1.tar.bz2
[lldb/ObjectFileMachO] Correctly account for resolver symbols
Summary: The resolver addresses stored in the dyld trie are relative to the base of the __TEXT segment. This is usually 0 in a dylib, so this was never noticed, but it is not 0 for most dylibs integrated in the shared cache. As we started using the shared cache images recently as symbol source, this causes LLDB to fail to resolve symbols which go through a runtime resolver. Reviewers: jasonmolenda, jingham Subscribers: lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D84083
Diffstat (limited to 'llvm/lib/Analysis/ValueTracking.cpp')
0 files changed, 0 insertions, 0 deletions