What Developers Really Struggle With When Debugging Rust: 2026 Survey Results

The Rust team has launched a Rust Debugging Survey, inviting developers to share their firsthand experiences with one of the language's most persistent pain points.

Debugging Rust code ranks among the most frequently cited challenges in the Rust developer ecosystem. While functional debugging workflows do exist today, coverage remains uneven — with notable gaps in toolchain compatibility, platform support, and the handling of language-specific constructs. The quality of the debugging experience varies considerably depending on which debugger a developer reaches for and which operating system they're targeting.

For Rust to achieve truly world-class debugging support, the team has identified several foundational capabilities that need to be addressed:

• Broad compatibility across multiple versions of major debuggers — including GDB, LLDB, and CDB — on a variety of operating systems.
• Robust debugger visualizers capable of rendering Rust's rich type system in a clear, developer-friendly format.
• First-class support for inspecting and stepping through async code, a particularly complex challenge given Rust's ownership and concurrency model.
• The ability to evaluate arbitrary Rust expressions directly within the debugger context.

Reaching that benchmark is an ambitious undertaking. Beyond the initial implementation effort, maintaining a reliable debugging experience over time presents its own set of difficulties — from keeping pace with newly released debugger versions to accommodating internal changes in how Rust's standard library represents data structures, any of which can silently degrade the debugging experience for end users.

The team already has concrete plans underway to strengthen debugging infrastructure, including improvements to the Rust compiler's debuginfo test suite. However, targeted community feedback is equally essential to prioritizing the right areas for improvement. The Rust Debugging Survey is designed precisely to surface the specific friction points that developers encounter in their day-to-day workflows.

Developers can complete the survey here.

The survey is estimated to take approximately five minutes to complete and is fully anonymous. Submissions will be accepted through Friday, March 13th, 2026. Once the collection period closes, the team will analyze the results and publish key findings on the official Rust blog.

Special recognition goes to Sam Kellam (@hashcatHitman), whose significant contributions were instrumental in designing and preparing the survey.

Every response strengthens the team's ability to make targeted, meaningful improvements to the Rust debugging experience. Developers of all experience levels are encouraged to participate and make their voices heard.