[Lldb-commits] [lldb] d9291f1 - [lldb][docs] Fix doc link syntax in bytecode formatter doc

[David Spickett via lldb-commits]

Author: David Spickett
Date: 2025-12-10T09:56:32Z
New Revision: d9291f18ec1a9434b63995bd6e519f4968138b5a

URL: https://github.com/llvm/llvm-project/commit/d9291f18ec1a9434b63995bd6e519f4968138b5a
DIFF: https://github.com/llvm/llvm-project/commit/d9291f18ec1a9434b63995bd6e519f4968138b5a.diff

LOG: [lldb][docs] Fix doc link syntax in bytecode formatter doc

This was flagged after the changes in 53674e2da437646591a6d20397cfd6c645dbf250.

Fixes warning:
formatterbytecode.rst:7: WARNING: 'any' reference target not found: ). To use custom data formatters, developers need to edit the global ``~/.lldbinit`

Added: 
    

Modified: 
    lldb/docs/resources/formatterbytecode.rst

Removed: 
    


################################################################################
diff  --git a/lldb/docs/resources/formatterbytecode.rst b/lldb/docs/resources/formatterbytecode.rst
index ad2f0e75a275f..c1b9f931d18f1 100644
--- a/lldb/docs/resources/formatterbytecode.rst
+++ b/lldb/docs/resources/formatterbytecode.rst
@@ -4,7 +4,7 @@ Formatter Bytecode
 Background
 ----------
 
-LLDB provides rich customization options to display data types (see :doc`/use/variable/`). To use custom data formatters, developers need to edit the global ``~/.lldbinit`` file to make sure they are found and loaded. In addition to this rather manual workflow, developers or library authors can ship ship data formatters with their code in a format that allows LLDB automatically find them and run them securely.
+LLDB provides rich customization options to display data types (see :doc:`/use/variable/`). To use custom data formatters, developers need to edit the global ``~/.lldbinit`` file to make sure they are found and loaded. In addition to this rather manual workflow, developers or library authors can ship ship data formatters with their code in a format that allows LLDB automatically find them and run them securely.
 
 An end-to-end example of such a workflow is the Swift ``DebugDescription`` macro (see https://www.swift.org/blog/announcing-swift-6/#debugging ) that translates Swift string interpolation into LLDB summary strings, and puts them into a ``.lldbsummaries`` section, where LLDB can find them.