diff options
| author | Kuba Mracek <mracek@apple.com> | 2018-10-24 18:40:08 +0000 |
|---|---|---|
| committer | Kuba Mracek <mracek@apple.com> | 2018-10-24 18:40:08 +0000 |
| commit | 6b6d9bbd48c1079b06404059eb2ea37b913b0d27 (patch) | |
| tree | 3be214150a9f96992e7210744a94b33a5ae01e3e /lldb/packages/Python/lldbsuite/test/python_api/frame | |
| parent | 5efe8ec4cd09d73c82a15ada6cedcacbf695c6d2 (diff) | |
| download | bcm5719-llvm-6b6d9bbd48c1079b06404059eb2ea37b913b0d27.tar.gz bcm5719-llvm-6b6d9bbd48c1079b06404059eb2ea37b913b0d27.zip | |
[sanitizer] Avoid calling a nullptr in MonotonicNanoTime if interceptors are not yet initialized
There's a TSan startup crash on Linux when used in Swift programs, where MonotonicNanoTime will try to call real_clock_gettime and then jump to NULL because interceptors are not yet initialized. This is on Ubuntu 18.04. Looks like TSan's main Initialize() function is called at a point where __progname is already set, but interceptors aren't yet set up. Let's fix this by checking whether interceptors are initialized in MonotonicNanoTime.
Differential Revision: https://reviews.llvm.org/D53528
llvm-svn: 345174
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/frame')
0 files changed, 0 insertions, 0 deletions
