From 15d1b4e2aab9159a8cc56b49eb68f1a82e4ebe90 Mon Sep 17 00:00:00 2001 From: Enrico Granata Date: Tue, 12 Apr 2016 18:23:18 +0000 Subject: Initialize the Python script interpreter lazily (i.e. not at debugger startup) This time it should also pass the gtests llvm-svn: 266103 --- lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp | 1 + 1 file changed, 1 insertion(+) (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 3d1727dc1c2..5eb1c72598a 100644 --- a/lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp +++ b/lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp @@ -24,6 +24,7 @@ PythonTestSuite::SetUp() // ScriptInterpreterPython::Initialize() depends on HostInfo being // initializedso it can compute the python directory etc. ScriptInterpreterPython::Initialize(); + ScriptInterpreterPython::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.2.3