*** This commit represents a complete reformatting of the LLDB source code

*** to conform to clang-format’s LLVM style.  This kind of mass change has
*** two obvious implications:

Firstly, merging this particular commit into a downstream fork may be a huge
effort.  Alternatively, it may be worth merging all changes up to this commit,
performing the same reformatting operation locally, and then discarding the
merge for this particular commit.  The commands used to accomplish this
reformatting were as follows (with current working directory as the root of
the repository):

    find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} +
    find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ;

The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.

Secondly, “blame” style tools will generally point to this commit instead of
a meaningful prior commit.  There are alternatives available that will attempt
to look through this change and find the appropriate prior commit.  YMMV.

llvm-svn: 280751

1 files changed, 22 insertions, 16 deletions

diff --git a/lldb/packages/Python/lldbsuite/test/functionalities/multidebugger_commands/TestMultipleDebuggersCommands.py b/lldb/packages/Python/lldbsuite/test/functionalities/multidebugger_commands/TestMultipleDebuggersCommands.py
index 7d959ec504c..9cdd7158516 100644
--- a/lldb/packages/Python/lldbsuite/test/functionalities/multidebugger_commands/TestMultipleDebuggersCommands.py
+++ b/lldb/packages/Python/lldbsuite/test/functionalities/multidebugger_commands/TestMultipleDebuggersCommands.py
@@ -5,13 +5,14 @@ Test that commands do not try and hold on to stale CommandInterpreters in a mult
 from __future__ import print_function
 
 
-
-import os, time
+import os
+import time
 import lldb
 from lldbsuite.test.decorators import *
 from lldbsuite.test.lldbtest import *
 from lldbsuite.test import lldbutil
 
+
 class MultipleDebuggersCommandsTestCase(TestBase):
 
     mydir = TestBase.compute_mydir(__file__)
@@ -21,28 +22,33 @@ class MultipleDebuggersCommandsTestCase(TestBase):
         """Test that commands do not try and hold on to stale CommandInterpreters in a multiple debuggers scenario"""
         source_init_files = False
         magic_text = "The following commands may relate to 'env'"
-        
+
         debugger_1 = lldb.SBDebugger.Create(source_init_files)
         interpreter_1 = debugger_1.GetCommandInterpreter()
-        
+
         retobj = lldb.SBCommandReturnObject()
         interpreter_1.HandleCommand("apropos env", retobj)
-        self.assertTrue(magic_text in str(retobj), "[interpreter_1]: the output does not contain the correct words")
-        
-        if self.TraceOn(): print(str(retobj))
-        
+        self.assertTrue(
+            magic_text in str(retobj),
+            "[interpreter_1]: the output does not contain the correct words")
+
+        if self.TraceOn():
+            print(str(retobj))
+
         lldb.SBDebugger.Destroy(debugger_1)
-        
+
         # now do this again with a different debugger - we shouldn't crash
-        
+
         debugger_2 = lldb.SBDebugger.Create(source_init_files)
         interpreter_2 = debugger_2.GetCommandInterpreter()
-        
+
         retobj = lldb.SBCommandReturnObject()
         interpreter_2.HandleCommand("apropos env", retobj)
-        self.assertTrue(magic_text in str(retobj), "[interpreter_2]: the output does not contain the correct words")
-        
-        if self.TraceOn(): print(str(retobj))
-        
+        self.assertTrue(
+            magic_text in str(retobj),
+            "[interpreter_2]: the output does not contain the correct words")
+
+        if self.TraceOn():
+            print(str(retobj))
+
         lldb.SBDebugger.Destroy(debugger_2)
-