• We’re launching a Rust Debugging Survey. • Various issues with debugging Rust code are often mentioned as one of the biggest challenges that annoy Rust developers. • While it is definitely possible to debug Rust code today, there are situations where it does not work well enough, and the quality of debugging support also varies a lot across different debuggers and operating systems. • In order for Rust to have truly stellar debugging support, it should ideally: - Support (several versions!) of different debuggers (such as GDB, LLDB or CDB) across multiple operating systems. • - Implement debugger visualizers that are able to produce quality presentation of most Rust types. • - Provide first-class support for debugging async code.

Article Summaries:

  • Rust Debugging Survey 2026

The Rust project has announced a new survey to gauge developers’ debugging challenges. While Rust can be debugged today, users report inconsistent support across debuggers (GDB, LLDB, CDB) and operating systems, limited visualizers for Rust types, poor async‑code debugging, and difficulty evaluating expressions. The survey aims to identify specific pain points and guide future improvements. It is open until Friday, March 13, 2026, and will take about five minutes to complete. Results will be analyzed and shared on the Rust blog to inform ongoing efforts to enhance debugging quality.

  • We’re launching a Rust Debugging Survey. Various issues with debugging Rust code are often mentioned as one of the biggest challenges that annoy Rust developers. While it is definitely possible to debug Rust code today, there are situations where it does not work well enough, and the quality of debugging support also varies a lot across different debuggers and operating systems. In order for Rust to have truly stellar debugging support, it should ideally: - Support (several versions!) of different debuggers (such as GDB, LLDB or CDB) across multiple operating systems. - Implement debugger visu

Sources: