summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp
diff options
context:
space:
mode:
authorAlexander Potapenko <glider@google.com>2017-12-11 15:05:22 +0000
committerAlexander Potapenko <glider@google.com>2017-12-11 15:05:22 +0000
commitc07e6a0eff976564060fb09400e637c5df03d564 (patch)
tree25160196b7d5d45d4f2215105dea4565c86d94b2 /lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp
parent830a45355446c7d4cbbbe9b09b53cbaa822c20df (diff)
downloadbcm5719-llvm-c07e6a0eff976564060fb09400e637c5df03d564.tar.gz
bcm5719-llvm-c07e6a0eff976564060fb09400e637c5df03d564.zip
[MSan] introduce getShadowOriginPtr(). NFC.
This patch introduces getShadowOriginPtr(), a method that obtains both the shadow and origin pointers for an address as a Value pair. The existing callers of getShadowPtr() and getOriginPtr() are updated to use getShadowOriginPtr(). The rationale for this change is to simplify KMSAN instrumentation implementation. In KMSAN origins tracking is always enabled, and there's no direct mapping between the app memory and the shadow/origin pages. Both the shadow and the origin pointer for a given address are obtained by calling a single runtime hook from the instrumentation, therefore it's easier to work with those pointers together. Reviewed at https://reviews.llvm.org/D40835. llvm-svn: 320373
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud