Switching debuggers and renderers
Choosing a debugger (Windows, Linux)
On Windows, the toolchain configured for your project determines the debugger you can use:
MSVC toolchain. If you are using Rust's MSVC toolchain, you can only debug code with LLDB.
GNU toolchain. With a GNU toolchain, you must use GDB.
RustRover will notify you if the active debugger does not match the project's toolchain:
On Linux, you are free to choose between LLDB and GDB. Both debuggers are bundled, LLDB is enabled by default.
On macOS, you can only use LLDB. It is bundled and enabled by default.
Switch debuggers (Windows, Linux)
Locate the Rust section and select the preferred debugger from the drop-down list.
Rust type renderers (pretty-printers)
You can switch the renderers RustRover uses to display Rust types in the Variables pane.
For the debugger in use, select an option from the drop-down list:
No renderers. This option disables explicit rendering, leaving only the type support provided by GDB or LLDB natively. Because Rust type formatters are currently not available in LLDB and GDB out of the box, this option means no rendering for types other than C/C++ types.
Rust compiler’s renderers. With this option, RustRover takes pretty-printers from the standard rustc distribution and loads them onto the debugger.
Bundled renderers. The IDE’s own renderers are implemented from scratch for both GDB and LLDB, unifying type representation for the two debuggers. These formatters build tree views for strings, structs, enums, and vectors, making it easier for you to look inside child elements.
The bundled renderers also support standard library types like
Ref, and others.