aboutsummaryrefslogtreecommitdiff
path: root/lldb/unittests/ScriptInterpreter/Python
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2022-01-19 09:16:16 -0800
committerJonas Devlieghere <jonas@devlieghere.com>2022-01-19 09:56:55 -0800
commiteb5c0ea681803361a1944c966f4becaa9e22dc1a (patch)
tree1dab18243e015d5db2e96efb7539c0e1ccd28a6b /lldb/unittests/ScriptInterpreter/Python
parent85c2bd2a0e0e2c1706bbf50203d5bbbeedbbd741 (diff)
downloadllvm-eb5c0ea681803361a1944c966f4becaa9e22dc1a.zip
llvm-eb5c0ea681803361a1944c966f4becaa9e22dc1a.tar.gz
llvm-eb5c0ea681803361a1944c966f4becaa9e22dc1a.tar.bz2
[lldb] Initialize Python exactly once
We got a few crash reports that showed LLDB initializing Python on two separate threads. Make sure Python is initialized exactly once. rdar://87287005 Differential revision: https://reviews.llvm.org/D117601
Diffstat (limited to 'lldb/unittests/ScriptInterpreter/Python')
-rw-r--r--lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp2
1 files changed, 0 insertions, 2 deletions
diff --git a/lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp b/lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp
index ba96cc6..a0e97a2 100644
--- a/lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp
+++ b/lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp
@@ -22,7 +22,6 @@ using namespace lldb_private;
class TestScriptInterpreterPython : public ScriptInterpreterPythonImpl {
public:
using ScriptInterpreterPythonImpl::Initialize;
- using ScriptInterpreterPythonImpl::InitializePrivate;
};
void PythonTestSuite::SetUp() {
@@ -31,7 +30,6 @@ void PythonTestSuite::SetUp() {
// ScriptInterpreterPython::Initialize() depends on HostInfo being
// initializedso it can compute the python directory etc.
TestScriptInterpreterPython::Initialize();
- TestScriptInterpreterPython::InitializePrivate();
// Although we don't care about concurrency for the purposes of running
// this test suite, Python requires the GIL to be locked even for