Add identifier syntax to attributes.debugger

Author: chorman0773

src/attributes/debugger.md

@@ -1,20 +1,32 @@
 # Debugger attributes
 
+r[attributes.debugger]
+
 The following [attributes] are used for enhancing the debugging experience when using third-party debuggers like GDB or WinDbg.
 
 ## The `debugger_visualizer` attribute
 
+r[attributes.debugger.debugger_visualizer]
+
+r[attributes.debugger.debugger_visualizer.general]
 The *`debugger_visualizer` attribute* can be used to embed a debugger visualizer file into the debug information.
 This enables an improved debugger experience for displaying values in the debugger.
+
+r[attributes.debugger.debugger_visualizer.restriction]
 It uses the [_MetaListNameValueStr_] syntax to specify its inputs, and must be specified as a crate attribute.
 
 ### Using `debugger_visualizer` with Natvis
 
+r[attributes.debugger.debugger_visualizer.natvis]
+
+r[attributes.debugger.debugger_visualizer.natvis-general]
 Natvis is an XML-based framework for Microsoft debuggers (such as Visual Studio and WinDbg) that uses declarative rules to customize the display of types.
 For detailed information on the Natvis format, refer to Microsoft's [Natvis documentation].
 
+r[attributes.debugger.debugger_visualizer.natvis-restrictions]
 This attribute only supports embedding Natvis files on `-windows-msvc` targets.
 
+r[attributes.debugger.debugger_visualizer.natvis-path]
 The path to the Natvis file is specified with the `natvis_file` key, which is a path relative to the crate source file:
 
 <!-- ignore: requires external files, and msvc -->
@@ -72,6 +84,10 @@ When viewed under WinDbg, the `fancy_rect` variable would be shown as follows:
 
 ### Using `debugger_visualizer` with GDB
 
+r[attributes.debugger.debugger_visualizer.gdb]
+
+
+r[attributes.debugger.debugger_visualizer.gdb-pretty]
 GDB supports the use of a structured Python script, called a *pretty printer*, that describes how a type should be visualized in the debugger view.
 For detailed information on pretty printers, refer to GDB's [pretty printing documentation].
 
@@ -81,6 +97,7 @@ There are two ways to enable auto-loading embedded pretty printers:
  For more information, see GDB's [auto-loading documentation].
 1. Create a file named `gdbinit` under `$HOME/.config/gdb` (you may need to create the directory if it doesn't already exist). Add the following line to that file: `add-auto-load-safe-path path/to/binary`.
 
+r[attributes.debugger.debugger_visualizer.gdb-path]
 These scripts are embedded using the `gdb_script_file` key, which is a path relative to the crate source file.
 
 <!-- ignore: requires external files -->
@@ -142,16 +159,23 @@ When the crate's debug executable is passed into GDB[^rust-gdb], `print bob` wil
 
 ## The `collapse_debuginfo` attribute
 
+r[attributes.debugger.collapse_debuginfo]
+
+
+r[attributes.debugger.collapse_debuginfo.general]
 The *`collapse_debuginfo` [attribute]* controls whether code locations from a macro definition are collapsed into a single location associated with the macro's call site,
 when generating debuginfo for code calling this macro.
 
+r[attributes.debugger.collapse_debuginfo.syntax]
 The attribute uses the [_MetaListIdents_] syntax to specify its inputs, and can only be applied to macro definitions.
 
+r[attributes.debugger.collapse_debuginfo.options]
 Accepted options:
 - `#[collapse_debuginfo(yes)]` --- code locations in debuginfo are collapsed.
 - `#[collapse_debuginfo(no)]` --- code locations in debuginfo are not collapsed.
 - `#[collapse_debuginfo(external)]` --- code locations in debuginfo are collapsed only if the macro comes from a different crate.
 
+r[attributes.debugger.collapse_debuginfo.default]
 The `external` behavior is the default for macros that don't have this attribute, unless they are built-in macros.
 For built-in macros the default is `yes`.