[lldb][docs] Translate ASCII art to restructured text formatting

This translates most of the old ASCII art in our documentation to the
equivalent in restructured text (which the new version of the LLDB docs
is using).

Author: Teemperor

lldb/bindings/interface/SBAddress.i

@@ -17,8 +17,9 @@ libraries, bundles, frameworks) being loaded at different
 addresses than the addresses found in the object file that
 represents them on disk. There are currently two types of addresses
 for a section:
-    o file addresses
-    o load addresses
+
+* file addresses
+* load addresses
 
 File addresses represents the virtual addresses that are in the 'on
 disk' object files. These virtual addresses are converted to be

lldb/bindings/interface/SBBreakpoint.i

@@ -11,7 +11,7 @@ namespace lldb {
 "Represents a logical breakpoint and its associated settings.
 
 For example (from test/functionalities/breakpoint/breakpoint_ignore_count/
-TestBreakpointIgnoreCount.py),
+TestBreakpointIgnoreCount.py),::
 
     def breakpoint_ignore_count_python(self):
         '''Use Python APIs to set breakpoint ignore count.'''
@@ -62,13 +62,13 @@ TestBreakpointIgnoreCount.py),
 
         process.Continue()
 
-SBBreakpoint supports breakpoint location iteration, for example,
+SBBreakpoint supports breakpoint location iteration, for example,::
 
     for bl in breakpoint:
         print('breakpoint location load addr: %s' % hex(bl.GetLoadAddress()))
         print('breakpoint location condition: %s' % hex(bl.GetCondition()))
 
-and rich comparison methods which allow the API program to use,
+and rich comparison methods which allow the API program to use,::
 
     if aBreakpoint == bBreakpoint:
         ...
@@ -102,7 +102,7 @@ public:
 
     lldb::SBTarget
     GetTarget() const;
-  
+
     lldb::SBBreakpointLocation
     FindLocationByAddress (lldb::addr_t vm_addr);
 

lldb/bindings/interface/SBBreakpointLocation.i

@@ -15,7 +15,7 @@ A breakpoint location is defined by the breakpoint that produces it,
 and the address that resulted in this particular instantiation.
 Each breakpoint location has its settable options.
 
-SBBreakpoint contains SBBreakpointLocation(s). See docstring of SBBreakpoint
+:py:class:`SBBreakpoint` contains SBBreakpointLocation(s). See docstring of SBBreakpoint
 for retrieval of an SBBreakpointLocation from an SBBreakpoint."
 ) SBBreakpointLocation;
 class SBBreakpointLocation

lldb/bindings/interface/SBBreakpointName.i

@@ -8,12 +8,12 @@
 
 namespace lldb {
 %feature("docstring",
-"Represents a breakpoint name registered in a given SBTarget.
+"Represents a breakpoint name registered in a given :py:class:`SBTarget`.
 
 Breakpoint names provide a way to act on groups of breakpoints.  When you add a
 name to a group of breakpoints, you can then use the name in all the command
 line lldb commands for that name.  You can also configure the SBBreakpointName
-options and those options will be propagated to any SBBreakpoints currently
+options and those options will be propagated to any :py:class:`SBBreakpoint` s currently
 using that name.  Adding a name to a breakpoint will also apply any of the
 set options to that breakpoint.
 

lldb/bindings/interface/SBCommandInterpreter.i

@@ -9,9 +9,11 @@
 namespace lldb {
 
 %feature("docstring",
-"SBCommandInterpreter handles/interprets commands for lldb.  You get the
-command interpreter from the SBDebugger instance. For example (from test/
-python_api/interpreter/TestCommandInterpreterAPI.py),
+"SBCommandInterpreter handles/interprets commands for lldb.
+
+You get the command interpreter from the :py:class:`SBDebugger` instance.
+
+For example (from test/ python_api/interpreter/TestCommandInterpreterAPI.py),::
 
     def command_interpreter_api(self):
         '''Test the SBCommandInterpreter APIs.'''

lldb/bindings/interface/SBCommandInterpreterRunOptions.i

@@ -10,13 +10,14 @@ namespace lldb {
 
 %feature("docstring",
 "SBCommandInterpreterRunOptions controls how the RunCommandInterpreter runs the code it is fed.
+
 A default SBCommandInterpreterRunOptions object has:
-    StopOnContinue: false
-    StopOnError:    false
-    StopOnCrash:    false
-    EchoCommands:   true
-    PrintResults:   true
-    AddToHistory:   true
+* StopOnContinue: false
+* StopOnError:    false
+* StopOnCrash:    false
+* EchoCommands:   true
+* PrintResults:   true
+* AddToHistory:   true
 
 ") SBCommandInterpreterRunOptions;
 class SBCommandInterpreterRunOptions

lldb/bindings/interface/SBCommandReturnObject.i

@@ -10,10 +10,10 @@ namespace lldb {
 
 %feature("docstring",
 "Represents a container which holds the result from command execution.
-It works with SBCommandInterpreter.HandleCommand() to encapsulate the result
+It works with :py:class:`SBCommandInterpreter.HandleCommand()` to encapsulate the result
 of command execution.
 
-See SBCommandInterpreter for example usage of SBCommandReturnObject."
+See :py:class:`SBCommandInterpreter` for example usage of SBCommandReturnObject."
 ) SBCommandReturnObject;
 class SBCommandReturnObject
 {

lldb/bindings/interface/SBCompileUnit.i

@@ -11,7 +11,7 @@ namespace lldb {
 %feature("docstring",
 "Represents a compilation unit, or compiled source file.
 
-SBCompileUnit supports line entry iteration. For example,
+SBCompileUnit supports line entry iteration. For example,::
 
     # Now get the SBSymbolContext from this frame.  We want everything. :-)
     context = frame0.GetSymbolContext(lldb.eSymbolContextEverything)
@@ -25,23 +25,23 @@ SBCompileUnit supports line entry iteration. For example,
         print('start addr: %s' % str(lineEntry.GetStartAddress()))
         print('end   addr: %s' % str(lineEntry.GetEndAddress()))
 
-produces:
-
-line entry: /Volumes/data/lldb/svn/trunk/test/python_api/symbol-context/main.c:20
-start addr: a.out[0x100000d98]
-end   addr: a.out[0x100000da3]
-line entry: /Volumes/data/lldb/svn/trunk/test/python_api/symbol-context/main.c:21
-start addr: a.out[0x100000da3]
-end   addr: a.out[0x100000da9]
-line entry: /Volumes/data/lldb/svn/trunk/test/python_api/symbol-context/main.c:22
-start addr: a.out[0x100000da9]
-end   addr: a.out[0x100000db6]
-line entry: /Volumes/data/lldb/svn/trunk/test/python_api/symbol-context/main.c:23
-start addr: a.out[0x100000db6]
-end   addr: a.out[0x100000dbc]
-...
-
-See also SBSymbolContext and SBLineEntry"
+produces: ::
+
+  line entry: /Volumes/data/lldb/svn/trunk/test/python_api/symbol-context/main.c:20
+  start addr: a.out[0x100000d98]
+  end   addr: a.out[0x100000da3]
+  line entry: /Volumes/data/lldb/svn/trunk/test/python_api/symbol-context/main.c:21
+  start addr: a.out[0x100000da3]
+  end   addr: a.out[0x100000da9]
+  line entry: /Volumes/data/lldb/svn/trunk/test/python_api/symbol-context/main.c:22
+  start addr: a.out[0x100000da9]
+  end   addr: a.out[0x100000db6]
+  line entry: /Volumes/data/lldb/svn/trunk/test/python_api/symbol-context/main.c:23
+  start addr: a.out[0x100000db6]
+  end   addr: a.out[0x100000dbc]
+  ...
+
+See also :py:class:`SBSymbolContext` and :py:class:`SBLineEntry`"
 ) SBCompileUnit;
 class SBCompileUnit
 {

lldb/bindings/interface/SBEnvironment.i

@@ -11,7 +11,8 @@ namespace lldb {
 %feature("docstring",
 "Represents the environment of a certain process.
 
-Example:
+Example: ::
+
   for entry in lldb.debugger.GetSelectedTarget().GetEnvironment().GetEntries():
     print(entry)
 

lldb/bindings/interface/SBError.i

@@ -11,7 +11,7 @@ namespace lldb {
 %feature("docstring",
 "Represents a container for holding any error code.
 
-For example (from test/python_api/hello_world/TestHelloWorld.py),
+For example (from test/python_api/hello_world/TestHelloWorld.py), ::
 
     def hello_world_attach_with_id_api(self):
         '''Create target, spawn a process, and attach to it by id.'''
@@ -45,7 +45,7 @@ For example (from test/python_api/hello_world/TestHelloWorld.py),
 checks that after the attach, there is no error condition by asserting
 that error.Success() is True and we get back a valid process object.
 
-And (from test/python_api/event/TestEvent.py),
+And (from test/python_api/event/TestEvent.py), ::
 
         # Now launch the process, and do not stop at entry point.
         error = lldb.SBError()