Rust Debugging

mohitmishra786/low-level-dev-skills/skills/rust/rust-debugging

作者 mohitmishra786bdc58472fa9f无许可证253 个星标收录于 2026年10月9日更新于 2026年10月9日仓库3个月前更新

Rust debugging skill for systems programming. Use when debugging Rust binaries with GDB or LLDB, enabling Rust pretty-printers, interpreting panics and backtraces, debugging async/await with tokio-console, stepping through no_std code, or using dbg! and tracing macros effectively. Activates on queries about rust-gdb, rust-lldb, RUST_BACKTRACE, Rust panics, debugging async Rust, tokio-console, or pretty-printers.

仅含说明Software Development
AI 生成的概览

指导使用 GDB/LLDB、回溯、panic 排查、异步追踪和 no_std 策略来调试 Rust 程序。

功能
该技能提供调试 Rust 二进制的操作指引：带调试信息构建、使用 rust-gdb 与 rust-lldb 及 Rust pretty-printer、配置 RUST_BACKTRACE、排查常见 panic 信息，以及使用 dbg! 宏和 tracing 进行结构化日志记录。它还涵盖使用 tokio-console 调试异步代码以及单步调试 no_std 代码。产出为指引和命令参考，而非可执行工具，并附带一份关于 GDB pretty-printer 配置的参考文档。
适用场景
适用于排查 Rust 崩溃、panic 或回溯，GDB 或 LLDB 的 pretty-printer 无法正确显示 String、Vec 或 Option 值时，或调试异步 Tokio 任务与 no_std 目标时。
运行要求
需要 Rust 工具链（含 cargo），以及 GDB 或 LLDB 等调试器及 rust-gdb/rust-lldb 包装脚本。可选依赖包括 tracing 与 tracing-subscriber crate、console-subscriber 与 tokio，以及 tokio-console 可执行文件。该技能不附带脚本，仅为说明文档加一份参考文档。

Rust Debugging

Purpose

Guide agents through debugging Rust programs: GDB/LLDB with Rust pretty-printers, backtrace configuration, panic triage, async debugging with tokio-console, and #[no_std] debugging strategies.

Triggers

  • "How do I use GDB/LLDB to debug a Rust binary?"
  • "How do I get a full backtrace from a Rust panic?"
  • "How do I debug async Rust / Tokio?"
  • "Rust pretty-printers aren't working in GDB"
  • "How do I debug a Rust panic in production?"
  • "How do I use dbg! and tracing in Rust?"

Workflow

1. Build for debugging

bash
# Debug build (default) — full debug info, no optimizationcargo build
# Release with debug info (for profiling real workloads)cargo build --release --profile release-with-debug# Or configure in Cargo.toml:# [profile.release-with-debug]# inherits = "release"# debug = true
# Run directlycargo runcargo run -- arg1 arg2

2. GDB with Rust pretty-printers

bash
# Use rust-gdb wrapper (sets up pretty-printers automatically)rust-gdb target/debug/myapp
# Or set up manually in ~/.gdbinit:# python# import subprocess, sys# ...

Common GDB session for Rust:

gdb
# Basic(gdb) break main(gdb) run arg1 arg2(gdb) next           # step over(gdb) step           # step into(gdb) continue
# Rust-aware inspection(gdb) print my_string     # Shows String content via pretty-printer(gdb) print my_vec        # Shows Vec elements(gdb) print my_option     # Shows Some(value) or None(gdb) info locals
# Break on panic(gdb) break rust_panic(gdb) break core::panicking::panic
# Backtrace(gdb) bt              # Short backtrace(gdb) bt full         # Full with locals

3. LLDB with Rust pretty-printers

bash
# Use rust-lldb wrapperrust-lldb target/debug/myapp
# Manual setuplldb target/debug/myapp(lldb) command script import /path/to/rust/lib/rustlib/etc/lldb_lookup.py(lldb) command source /path/to/rust/lib/rustlib/etc/lldb_commands

Common LLDB session:

lldb
(lldb) b main::main(lldb) r arg1 arg2(lldb) n              # next (step over)(lldb) s              # step into(lldb) c              # continue(lldb) frame variable # show locals(lldb) p my_string    # print variable with pretty-printer(lldb) bt             # backtrace(lldb) bt all         # all threads

4. Backtrace configuration

bash
# Short backtrace (default on panic)RUST_BACKTRACE=1 ./myapp
# Full backtrace with all framesRUST_BACKTRACE=full ./myapp
# With symbols (requires debug build or separate debug info)RUST_BACKTRACE=full ./target/debug/myapp
# Capture backtrace programmaticallyuse std::backtrace::Backtrace;let bt = Backtrace::capture();eprintln!("{bt}");

For release binaries, keep debug symbols in a separate file:

bash
# Build release with debug infocargo build --releaseobjcopy --only-keep-debug target/release/myapp target/release/myapp.debugstrip --strip-debug target/release/myappobjcopy --add-gnu-debuglink=target/release/myapp.debug target/release/myapp

5. Panic triage

rust
// Set a custom panic hook for structured logginguse std::panic;
panic::set_hook(Box::new(|info| {    let backtrace = std::backtrace::Backtrace::force_capture();    eprintln!("PANIC: {info}");    eprintln!("{backtrace}");    // Log to file, send to Sentry, etc.}));

Common panic patterns:

Panic messageLikely cause
index out of bounds: the len is N but the index is MArray/vec OOB access
called Option::unwrap() on a None valueUnwrap on None
called Result::unwrap() on an Err valueUnwrap on error
attempt to subtract with overflowInteger underflow (debug build)
assertion failedFailed assert! or assert_eq!
stack overflowInfinite recursion

Use panic = "abort" in release to get a crash dump instead of unwind.

6. The dbg! macro

rust
// dbg! prints file, line, value and returns the valuelet result = dbg!(some_computation(x));// prints: [src/main.rs:15] some_computation(x) = 42
// Chain multiple valueslet (a, b) = dbg!((compute_a(), compute_b()));
// Inspect inside iterator chainslet sum: i32 = (0..10)    .filter(|x| dbg!(x % 2 == 0))    .map(|x| dbg!(x * x))    .sum();

7. Structured logging with tracing

toml
[dependencies]tracing = "0.1"tracing-subscriber = { version = "0.3", features = ["env-filter"] }
rust
use tracing::{debug, error, info, instrument, warn};
#[instrument]  // Auto-traces function entry/exit with argumentsfn process(id: u64, data: &str) -> Result<(), Error> {    debug!("Processing item");    info!(item_id = id, "Started processing");
    if data.is_empty() {        warn!(item_id = id, "Empty data");        return Err(Error::EmptyData);    }
    error!(item_id = id, err = ?some_result, "Failed");    Ok(())}
// Initialize in maintracing_subscriber::fmt()    .with_env_filter("myapp=debug,warn")    .init();
bash
# Control log levels at runtimeRUST_LOG=debug ./myappRUST_LOG=myapp::module=trace,warn ./myapp

8. Async debugging with tokio-console

toml
[dependencies]console-subscriber = "0.3"tokio = { version = "1", features = ["full", "tracing"] }
rust
// In mainconsole_subscriber::init();
bash
# Install and run tokio-consolecargo install tokio-consoletokio-console  # Connects to running Rust process at port 6669

tokio-console shows: task states, waker activity, blocked tasks, poll durations.

For GDB/LLDB command reference and pretty-printer setup, see references/rust-gdb-pretty-printers.md [blocked].

Related skills

  • Use skills/rust/rustc-basics for debug info flags and build configuration
  • Use skills/debuggers/gdb for GDB fundamentals
  • Use skills/debuggers/lldb for LLDB fundamentals
  • Use skills/rust/rust-sanitizers-miri for memory safety and undefined behaviour

来源与署名

来源：mohitmishra786/low-level-dev-skills位于skills/rust/rust-debugging提交bdc5847

许可证： 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

更多来自 mohitmishra786/low-level-dev-skills 的技能

Zig Debugging

mohitmishra786

指导使用 GDB、LLDB 调试 Zig 程序，解读 panic、错误返回追踪、日志记录及 IDE 配置。

Software Development2533个月前更新

Simd Intrinsics

mohitmishra786

指导使用 x86 SSE/AVX 与 ARM NEON 内建函数编写和诊断 SIMD 向量化。

Software Development2533个月前更新

Zig Cross

mohitmishra786

指导 Zig 交叉编译：目标三元组、CPU 特性、用 zig cc 编译 C、嵌入式与 WASM 目标。

Software Development2533个月前更新

Rustc Basics

mohitmishra786

指导 Rust 编译器配置：RUSTFLAGS、Cargo 配置文件、构建调优，以及查看 MIR 或汇编输出。

Software Development2533个月前更新

Zig Cinterop

mohitmishra786

指导 Zig 与 C 互操作：@cImport、translate-c、extern 与 packed 结构体，以及 C/Zig 混合构建。

Software Development2533个月前更新

Zig Build System

mohitmishra786

指导编写和调试 Zig 的 build.zig 文件，涵盖目标、C 源码、选项、测试与包清单。

Software Development2533个月前更新

更多Software Development技能

Playground

anthropics

精选

构建自包含的交互式 HTML 演练场，包含控件、实时预览和可复制的提示词输出。

Software Development37K今天更新

M5 Onboard

anthropics

精选

通过 USB 检测 M5Stack ESP32 开发板，刷写 UIFlow 2.0 固件并安装 MicroPython 应用包。

Software Development37K今天更新

Cardputer Buddy

anthropics

精选

指导迭代 Cardputer-Adv 的 MicroPython 应用包：添加应用、通过 USB 串口推送文件、查看日志并运行 REPL 命令。

Software Development37K今天更新

Web Design Guidelines

vercel-labs

精选

依据从远程来源获取的 Web Interface Guidelines 审查 UI 代码，并以 file:line 形式报告问题。

Software Development32K5周前更新

Vercel React Native Skills

vercel-labs

精选

React Native 与 Expo 最佳实践规则，涵盖列表性能、动画、导航、UI 模式、状态与 monorepo 配置。

Software Development32K5周前更新

Vercel React Best Practices

vercel-labs

精选

Vercel 的 React 与 Next.js 性能指南，以 70 条规则的形式用于编写、审查和重构代码。

Software Development32K5周前更新