[Lldb-commits] [lldb] r356950 - [PythonTestSuite] Fix usage of InitializePrivate in PythonTestSuite

[Jonas Devlieghere via lldb-commits]

Author: jdevlieghere
Date: Mon Mar 25 14:07:53 2019
New Revision: 356950

URL: http://llvm.org/viewvc/llvm-project?rev=356950&view=rev
Log:
[PythonTestSuite] Fix usage of InitializePrivate in PythonTestSuite

Modified:
    lldb/trunk/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp

Modified: lldb/trunk/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp?rev=356950&r1=356949&r2=356950&view=diff
==============================================================================
--- lldb/trunk/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp (original)
+++ lldb/trunk/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp Mon Mar 25 14:07:53 2019
@@ -16,14 +16,19 @@
 #include "PythonTestSuite.h"
 
 using namespace lldb_private;
+class TestScriptInterpreterPython : public ScriptInterpreterPython {
+public:
+  using ScriptInterpreterPython::Initialize;
+  using ScriptInterpreterPython::InitializePrivate;
+};
 
 void PythonTestSuite::SetUp() {
   FileSystem::Initialize();
   HostInfoBase::Initialize();
   // ScriptInterpreterPython::Initialize() depends on HostInfo being
   // initializedso it can compute the python directory etc.
-  ScriptInterpreterPython::Initialize();
-  ScriptInterpreterPython::InitializePrivate();
+  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
@@ -36,7 +41,7 @@ void PythonTestSuite::SetUp() {
 void PythonTestSuite::TearDown() {
   PyGILState_Release(m_gil_state);
 
-  ScriptInterpreterPython::Terminate();
+  TestScriptInterpreterPython::Terminate();
   HostInfoBase::Terminate();
   FileSystem::Terminate();
 }