diff options
| author | Kuba Brecka <kuba.brecka@gmail.com> | 2015-12-14 13:32:57 +0000 |
|---|---|---|
| committer | Kuba Brecka <kuba.brecka@gmail.com> | 2015-12-14 13:32:57 +0000 |
| commit | 2cdb522a5a1320ba915975551c3c3bebdcac4160 (patch) | |
| tree | a4d1cd841dc9fd30619637d8a238145c0fcacb70 /lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp | |
| parent | ffbf9e86b2e542cfff2b293e7eb9e2d535fc7cc8 (diff) | |
| download | bcm5719-llvm-2cdb522a5a1320ba915975551c3c3bebdcac4160.tar.gz bcm5719-llvm-2cdb522a5a1320ba915975551c3c3bebdcac4160.zip | |
[tsan] Update dispatch_group support to avoid using a disposed group object
We're using the dispatch group itself to synchronize (to call Release() and Acquire() on it), but in dispatch group notifications, the group can already be disposed/deallocated. This causes a later assertion failure at `DCHECK_EQ(*meta, 0);` in `MetaMap::AllocBlock` when the same memory is reused (note that the failure only happens in debug builds).
Fixing this by retaining the group and releasing it in the notification. Adding a stress test case that reproduces this.
Differential Revision: http://reviews.llvm.org/D15380
llvm-svn: 255494
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp')
0 files changed, 0 insertions, 0 deletions
