diff --git a/src/attributes/debugger.md b/src/attributes/debugger.md
index 9f4ec5c79..a7146a52b 100644
--- a/src/attributes/debugger.md
+++ b/src/attributes/debugger.md
@@ -3,148 +3,166 @@ r[attributes.debugger]
The following [attributes] are used for enhancing the debugging experience when using third-party debuggers like GDB or WinDbg.
+
r[attributes.debugger.debugger_visualizer]
## The `debugger_visualizer` attribute
r[attributes.debugger.debugger_visualizer.intro]
-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.
+The *`debugger_visualizer` [attribute][attributes]* can be used to embed a debugger visualizer file into the debug information. This improves the debugger experience when displaying values.
+
+> [!EXAMPLE]
+>
+> ```rust,ignore
+> #![debugger_visualizer(natvis_file = "Example.natvis")]
+> #![debugger_visualizer(gdb_script_file = "example.py")]
+> ```
r[attributes.debugger.debugger_visualizer.syntax]
-It uses the [MetaListNameValueStr] syntax to specify its inputs, and must be specified as a crate attribute.
+The `debugger_visualizer` attribute uses the [MetaListNameValueStr] syntax to specify its inputs. One of the following keys must be specified:
+
+- [`natvis_file`][attributes.debugger.debugger_visualizer.natvis]
+- [`gdb_script_file`][attributes.debugger.debugger_visualizer.gdb]
+
+r[attributes.debugger.debugger_visualizer.allowed-positions]
+The `debugger_visualizer` attribute may only be applied to a [module] or to the crate root.
+
+r[attributes.debugger.debugger_visualizer.duplicates]
+The `debugger_visualizer` attribute may be used any number of times on a form. All specified visualizer files will be loaded.
r[attributes.debugger.debugger_visualizer.natvis]
### Using `debugger_visualizer` with Natvis
r[attributes.debugger.debugger_visualizer.natvis.intro]
-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].
+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.msvc]
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:
-
-
-```rust ignore
-#![debugger_visualizer(natvis_file = "Rectangle.natvis")]
-
-struct FancyRect {
- x: f32,
- y: f32,
- dx: f32,
- dy: f32,
-}
-
-fn main() {
- let fancy_rect = FancyRect { x: 10.0, y: 10.0, dx: 5.0, dy: 5.0 };
- println!("set breakpoint here");
-}
-```
+The path to the Natvis file is specified with the `natvis_file` key, which is a path relative to the source file.
-and `Rectangle.natvis` contains:
-
-```xml
-
-
-
- ({x},{y}) + ({dx}, {dy})
-
-
- ({x}, {y})
-
-
- ({x}, {y + dy})
-
-
- ({x + dx}, {y + dy})
-
-
- ({x + dx}, {y})
-
-
-
-
-```
-
-When viewed under WinDbg, the `fancy_rect` variable would be shown as follows:
-
-```text
-> Variables:
- > fancy_rect: (10.0, 10.0) + (5.0, 5.0)
- > LowerLeft: (10.0, 10.0)
- > UpperLeft: (10.0, 15.0)
- > UpperRight: (15.0, 15.0)
- > LowerRight: (15.0, 10.0)
-```
+> [!EXAMPLE]
+>
+> ```rust ignore
+> #![debugger_visualizer(natvis_file = "Rectangle.natvis")]
+>
+> struct FancyRect {
+> x: f32,
+> y: f32,
+> dx: f32,
+> dy: f32,
+> }
+>
+> fn main() {
+> let fancy_rect = FancyRect { x: 10.0, y: 10.0, dx: 5.0, dy: 5.0 };
+> println!("set breakpoint here");
+> }
+> ```
+>
+> `Rectangle.natvis` contains:
+>
+> ```xml
+>
+>
+>
+> ({x},{y}) + ({dx}, {dy})
+>
+>
+> ({x}, {y})
+>
+>
+> ({x}, {y + dy})
+>
+>
+> ({x + dx}, {y + dy})
+>
+>
+> ({x + dx}, {y})
+>
+>
+>
+>
+> ```
+>
+> When viewed under WinDbg, the `fancy_rect` variable would be shown as follows:
+>
+> ```text
+> > Variables:
+> > fancy_rect: (10.0, 10.0) + (5.0, 5.0)
+> > LowerLeft: (10.0, 10.0)
+> > UpperLeft: (10.0, 15.0)
+> > UpperRight: (15.0, 15.0)
+> > LowerRight: (15.0, 10.0)
+> ```
r[attributes.debugger.debugger_visualizer.gdb]
### Using `debugger_visualizer` with 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].
+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].
-Embedded pretty printers are not automatically loaded when debugging a binary under GDB.
-There are two ways to enable auto-loading embedded pretty printers:
-1. Launch GDB with extra arguments to explicitly add a directory or binary to the auto-load safe path: `gdb -iex "add-auto-load-safe-path safe-path path/to/binary" path/to/binary`
- 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`.
+> [!NOTE]
+> Embedded pretty printers are not automatically loaded when debugging a binary under GDB.
+>
+> There are two ways to enable auto-loading embedded pretty printers:
+>
+> 1. Launch GDB with extra arguments to explicitly add a directory or binary to the auto-load safe path: `gdb -iex "add-auto-load-safe-path safe-path path/to/binary" path/to/binary` 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.
-
-
-```rust ignore
-#![debugger_visualizer(gdb_script_file = "printer.py")]
-
-struct Person {
- name: String,
- age: i32,
-}
-
-fn main() {
- let bob = Person { name: String::from("Bob"), age: 10 };
- println!("set breakpoint here");
-}
-```
+These scripts are embedded using the `gdb_script_file` key, which is a path relative to the source file.
-and `printer.py` contains:
-
-```python
-import gdb
-
-class PersonPrinter:
- "Print a Person"
-
- def __init__(self, val):
- self.val = val
- self.name = val["name"]
- self.age = int(val["age"])
-
- def to_string(self):
- return "{} is {} years old.".format(self.name, self.age)
-
-def lookup(val):
- lookup_tag = val.type.tag
- if lookup_tag is None:
- return None
- if "foo::Person" == lookup_tag:
- return PersonPrinter(val)
-
- return None
-
-gdb.current_objfile().pretty_printers.append(lookup)
-```
-
-When the crate's debug executable is passed into GDB[^rust-gdb], `print bob` will display:
-
-```text
-"Bob" is 10 years old.
-```
-
-[^rust-gdb]: Note: This assumes you are using the `rust-gdb` script which configures pretty-printers for standard library types like `String`.
+> [!EXAMPLE]
+>
+> ```rust ignore
+> #![debugger_visualizer(gdb_script_file = "printer.py")]
+>
+> struct Person {
+> name: String,
+> age: i32,
+> }
+>
+> fn main() {
+> let bob = Person { name: String::from("Bob"), age: 10 };
+> println!("set breakpoint here");
+> }
+> ```
+>
+> `printer.py` contains:
+>
+> ```python
+> import gdb
+>
+> class PersonPrinter:
+> "Print a Person"
+>
+> def __init__(self, val):
+> self.val = val
+> self.name = val["name"]
+> self.age = int(val["age"])
+>
+> def to_string(self):
+> return "{} is {} years old.".format(self.name, self.age)
+>
+> def lookup(val):
+> lookup_tag = val.type.tag
+> if lookup_tag is None:
+> return None
+> if "foo::Person" == lookup_tag:
+> return PersonPrinter(val)
+>
+> return None
+>
+> gdb.current_objfile().pretty_printers.append(lookup)
+> ```
+>
+> When the crate's debug executable is passed into GDB[^rust-gdb], `print bob` will display:
+>
+> ```text
+> "Bob" is 10 years old.
+> ```
+>
+> [^rust-gdb]: Note: This assumes you are using the `rust-gdb` script which configures pretty-printers for standard library types like `String`.
[auto-loading documentation]: https://sourceware.org/gdb/onlinedocs/gdb/Auto_002dloading-safe-path.html
[attributes]: ../attributes.md
@@ -206,3 +224,4 @@ The `external` behavior is the default for macros that don't have this attribute
[`-C collapse-macro-debuginfo`]: ../../rustc/codegen-options/index.html#collapse-macro-debuginfo
[`macro_rules` definition]: ../macros-by-example.md
[attribute]: ../attributes.md
+[module]: ../items/modules.md