summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lldbbench.py
diff options
context:
space:
mode:
authorKuba Mracek <mracek@apple.com>2017-07-12 23:29:21 +0000
committerKuba Mracek <mracek@apple.com>2017-07-12 23:29:21 +0000
commitc1e903be19c42e2bb0d3178b463657e4a94b27b2 (patch)
tree7f7cce92e0258fcf432162b56991d7f099234014 /lldb/packages/Python/lldbsuite/test/lldbbench.py
parent07df59b7b656e0817001e2c37566dc9919100950 (diff)
downloadbcm5719-llvm-c1e903be19c42e2bb0d3178b463657e4a94b27b2.tar.gz
bcm5719-llvm-c1e903be19c42e2bb0d3178b463657e4a94b27b2.zip
[asan] For iOS/AArch64, if the dynamic shadow doesn't fit, restrict the VM space
On iOS/AArch64, the address space is very limited and has a dynamic maximum address based on the configuration of the device. We're already using a dynamic shadow, and we find a large-enough "gap" in the VM where we place the shadow memory. In some cases and some device configuration, we might not be able to find a large-enough gap: E.g. if the main executable is linked against a large number of libraries that are not part of the system, these libraries can fragment the address space, and this happens before ASan starts initializing. This patch has a solution, where we have a "backup plan" when we cannot find a large-enough gap: We will restrict the address space (via MmapFixedNoAccess) to a limit, for which the shadow limit will fit. Differential Revision: https://reviews.llvm.org/D35098 llvm-svn: 307865
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbbench.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud