llvmbot wrote:
<!--LLVM PR SUMMARY COMMENT--> @llvm/pr-subscribers-lldb Author: Chelsea Cassanova (chelcassanova) <details> <summary>Changes</summary> This adds the option to use the `breakpoint()` keyword as a way to debug the API tests. --- Full diff: https://github.com/llvm/llvm-project/pull/89979.diff 1 Files Affected: - (modified) lldb/docs/resources/test.rst (+1-1) ``````````diff diff --git a/lldb/docs/resources/test.rst b/lldb/docs/resources/test.rst index 2b0e9010fe280a..d90d7012f1c860 100644 --- a/lldb/docs/resources/test.rst +++ b/lldb/docs/resources/test.rst @@ -602,7 +602,7 @@ will cause the script to print out the pid of the test and wait for a while until a debugger is attached. Then run ``lldb -p <pid>`` to attach. To instead debug a test's python source, edit the test and insert -``import pdb; pdb.set_trace()`` at the point you want to start debugging. In +``import pdb; pdb.set_trace()`` or ``breakpoint()`` (Python 3 only) at the point you want to start debugging. In addition to pdb's debugging facilities, lldb commands can be executed with the help of a pdb alias. For example ``lldb bt`` and ``lldb v some_var``. Add this line to your ``~/.pdbrc``: `````````` </details> https://github.com/llvm/llvm-project/pull/89979 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
