diff options
| author | Raphael Isemann <teemperor@gmail.com> | 2019-12-03 08:53:42 +0100 |
|---|---|---|
| committer | Raphael Isemann <teemperor@gmail.com> | 2019-12-03 09:18:44 +0100 |
| commit | 315600f480055f5143aaa245f25bd25221edfa91 (patch) | |
| tree | 7c9232d82934df44f2606fd055d10829d58a6aa0 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h | |
| parent | b5f295ffcec2fa7402e39eb1262acbd55a7d39f5 (diff) | |
| download | bcm5719-llvm-315600f480055f5143aaa245f25bd25221edfa91.tar.gz bcm5719-llvm-315600f480055f5143aaa245f25bd25221edfa91.zip | |
[lldb][NFC] Remove ThreadSafeSTLVector and ThreadSafeSTLMap and their use in ValueObjectSynthetic
Summary:
ThreadSafeSTLVector and ThreadSafeSTLMap are not useful for achieving any degree of thread safety in LLDB
and should be removed before they are used in more places. They are only used (unsurprisingly incorrectly) in
`ValueObjectSynthetic::GetChildAtIndex`, so this patch replaces their use there with a simple mutex with which
we guard the related data structures. This doesn't make ValueObjectSynthetic::GetChildAtIndex
any more thread-safe, but on the other hand it at least allows us to get rid of the ThreadSafeSTL* data structures
without changing the observable behaviour of ValueObjectSynthetic (beside that it is now a few bytes smaller).
Reviewers: labath, JDevlieghere, jingham
Reviewed By: labath
Subscribers: lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D70845
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h')
0 files changed, 0 insertions, 0 deletions
