llvmbot wrote:

<!--LLVM PR SUMMARY COMMENT-->

@llvm/pr-subscribers-lldb

Author: 苏灵素@夏日限定 (Surinrasu)

<details>
<summary>Changes</summary>



---
Full diff: https://github.com/llvm/llvm-project/pull/111326.diff


1 Files Affected:

- (modified) lldb/docs/use/tutorial.rst (+3-3) 


``````````diff
diff --git a/lldb/docs/use/tutorial.rst b/lldb/docs/use/tutorial.rst
index 76e8ac4aeab89c..7bfe1743b917f6 100644
--- a/lldb/docs/use/tutorial.rst
+++ b/lldb/docs/use/tutorial.rst
@@ -210,7 +210,7 @@ you will have to indicate these are not option markers by 
putting ``--`` after t
 command name, but before your command string.
 
 LLDB also has a built-in Python interpreter, which is accessible by the
-``"script`` command. All the functionality of the debugger is available as 
classes
+``script`` command. All the functionality of the debugger is available as 
classes
 in the Python interpreter, so the more complex commands that in GDB you would
 introduce with the ``define`` command can be done by writing Python functions
 using the LLDB Python library, then loading the scripts into your running
@@ -331,8 +331,8 @@ do:
 
 ::
 
-   (lldb) help <breakpt-id> <breakpt-id> -- Breakpoint ID's consist major and
-   minor numbers; the major etc...
+   (lldb) help <breakpt-id>
+   <breakpt-id> -- Breakpoint ID's consist major and minor numbers; the major 
etc...
 
 Breakpoint Names
 ----------------

``````````

</details>


https://github.com/llvm/llvm-project/pull/111326
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to