Change the call within lldb.py to 'SBDebugger.Initialize()' from 'lldb.SBDebugger.Initialize()'.
Inside the lldb module, there's no need (and as a matter of fact, incorrect) to specify the 'lldb'
module name.
Comment out the call to lldb.SBDebugger.Initialize() within the test driver itself, since it is
already done when we import the lldb.py module.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@116485 91177308-0d34-0410-b5e6-96231b3b80d8
diff --git a/scripts/Python/append-debugger-id.py b/scripts/Python/append-debugger-id.py
index 26460c8..474443a 100644
--- a/scripts/Python/append-debugger-id.py
+++ b/scripts/Python/append-debugger-id.py
@@ -5,6 +5,9 @@
# module (which was automatically generated via running swig), and
# initializes it to 0.
#
+# It also calls SBDebugger.Initialize() to initialize the lldb debugger
+# subsystem.
+#
import sys
@@ -21,7 +24,7 @@
print "Error: Unable to open file for appending: " + output_name
else:
f_out.write ("debugger_unique_id = 0\n");
- f_out.write ("lldb.SBDebugger.Initialize()\n");
+ f_out.write ("SBDebugger.Initialize()\n");
try:
f_out.close()
except IOError: