diff options
| author | Greg Clayton <gclayton@apple.com> | 2016-05-04 22:26:42 +0000 |
|---|---|---|
| committer | Greg Clayton <gclayton@apple.com> | 2016-05-04 22:26:42 +0000 |
| commit | 4329fe427167a219864e841e88a2bd4dd7cc98d6 (patch) | |
| tree | 5e7840a07c431202186be7acc5355fcfc0cf86e6 /lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py | |
| parent | 92a20a299ff2c7598169bb28ea82e67e3dc32fec (diff) | |
| download | bcm5719-llvm-4329fe427167a219864e841e88a2bd4dd7cc98d6.tar.gz bcm5719-llvm-4329fe427167a219864e841e88a2bd4dd7cc98d6.zip | |
Don't let two threads call Debugger::Clear simultaneously.
We don't want a mutex in debugger as it will cause A/B locking issues with the lldb_private::Target's mutex, but we do need to stop two threads from doing Debugger::Clear at the same time. We have seen issues with this with the C++ global destructor chain where the global debugger list is being destroyed and the Debugger::~Debugger() is calling it while another thread was in the middle of running that function.
<rdar://problem/26098913>
llvm-svn: 268563
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py')
0 files changed, 0 insertions, 0 deletions
