From eb5c0ea681803361a1944c966f4becaa9e22dc1a Mon Sep 17 00:00:00 2001 From: Jonas Devlieghere Date: Wed, 19 Jan 2022 09:16:16 -0800 Subject: [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 --- lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp | 2 -- 1 file changed, 2 deletions(-) (limited to 'lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp') 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 -- cgit v1.1