summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp
diff options
context:
space:
mode:
authorMaxim Ostapenko <m.ostapenko@partner.samsung.com>2016-02-08 08:30:57 +0000
committerMaxim Ostapenko <m.ostapenko@partner.samsung.com>2016-02-08 08:30:57 +0000
commitb1e3f60fb932b2273ac37d61fcc9777997a255f3 (patch)
treeb0e1fefab66f0b206f48c4134f69adb152d4b4d3 /lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp
parentde49845b05d90a2c8dc278850a5d74bf5853f932 (diff)
downloadbcm5719-llvm-b1e3f60fb932b2273ac37d61fcc9777997a255f3.tar.gz
bcm5719-llvm-b1e3f60fb932b2273ac37d61fcc9777997a255f3.zip
[asan] Introduce new hidden -asan-use-private-alias option.
As discussed in https://github.com/google/sanitizers/issues/398, with current implementation of poisoning globals we can have some CHECK failures or false positives in case of mixing instrumented and non-instrumented code due to ASan poisons innocent globals from non-sanitized binary/library. We can use private aliases to avoid such errors. In addition, to preserve ODR violation detection, we introduce new __odr_asan_gen_XXX symbol for each instrumented global that indicates if this global was already registered. To detect ODR violation in runtime, we should only check the value of indicator and report an error if it isn't equal to zero. Differential Revision: http://reviews.llvm.org/D15642 llvm-svn: 260075
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud