https://github.com/DavidSpickett created https://github.com/llvm/llvm-project/pull/221944
None >From 0ae507b0094bf68ae71840fd016ba38717472f4a Mon Sep 17 00:00:00 2001 From: David Spickett <[email protected]> Date: Tue, 8 Sep 2026 09:52:18 +0000 Subject: [PATCH] [lldb][docs] Remove duplicate title in test doc --- lldb/docs/resources/test.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/lldb/docs/resources/test.md b/lldb/docs/resources/test.md index 5097b972db9f6..711625133c4b1 100644 --- a/lldb/docs/resources/test.md +++ b/lldb/docs/resources/test.md @@ -463,18 +463,16 @@ If you need to fake part of the debug server but forward the rest to a real debug server, start by looking at the reverse execution tests which use `ReverseTestBase`. -### The debug server's handling of specific packets or sequences of packets - -Use an API test that sends fake traffic to a real `lldb-server`. The existing -tests in `lldb/test/API/tools/lldb-server` are your starting point. - ### The Debug Server’s Handling of Specific Packets or Sequences of Packets Generally you can check this using `lldb`'s own commands in a Shell or API -test. +test. If you need exact packets, you can use an API test that sends fake traffic +to a real `lldb-server`. The existing tests in `lldb/test/API/tools/lldb-server` +are your starting point. -However if you do not trust enough of the implementation yet to do that, -you can have the inferior process check things for you. +If you are using `lldb`'s own commands but you do not want to trust the +implementation of those commands, you can have the inferior process check things +for you. For example, to test register access the API test might: 1. Launch the inferior, which writes a known pattern to the register using _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
