-
Notifications
You must be signed in to change notification settings - Fork 321
Add Rust Debugging Survey 2026 blog post
#1784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
Kobzol
wants to merge
2
commits into
rust-lang:main
Choose a base branch
from
Kobzol:rust-debugging-survey-2026
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+35
−0
Draft
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| +++ | ||
| path = "2026/02/23/rust-debugging-survey-2026" | ||
| title = "Rust debugging survey 2026" | ||
| authors = ["Jakub Beránek"] | ||
|
|
||
| [extra] | ||
| team = "the compiler team" | ||
| team_url = "https://www.rust-lang.org/governance/teams/compiler" | ||
| +++ | ||
|
|
||
| We're launching a [Rust Debugging Survey][survey-link]. | ||
|
|
||
| Various issues with debugging Rust code are often mentioned as one of the biggest [challenges][annual-survey] 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. | ||
| - Allow evaluating Rust expressions in the debugger. | ||
|
|
||
| Rust is not quite there yet, and it will take a lot of work to reach that level of debugger support. Furthermore, it is also challenging to ensure that debugging Rust code *keeps* working well, across newly released debugger versions, changes to internal representation of Rust data structures in the standard library and other things that can break the debugging experience. | ||
|
|
||
| We already have some [plans][debug-test-suite-gsoc] to start improving debugging support in Rust, but it would also be useful to understand the current debugging struggles of Rust developers. That is why we have prepared the [Rust Debugging Survey][survey-link], which should help us find specific challenges with debugging Rust code. | ||
|
|
||
| **You can fill out the survey [here][survey-link].** | ||
|
|
||
| Filling the survey should take you approximately 5 minutes, and the survey is fully anonymous. We will accept submissions until Friday, March 13th, 2026. After the survey ends, we will evaluate the results and post key insights on this blog. | ||
|
|
||
| We would like to thank [@hashcatHitman](https://github.com/hashcatHitman) who did a lot of great work to prepare the survey. | ||
|
|
||
| We invite you to fill the survey, as your responses will help us improve the Rust debugging experience. Thank you! | ||
|
|
||
| [annual-survey]: https://blog.rust-lang.org/2025/02/13/2024-State-Of-Rust-Survey-results/#challenges | ||
| [survey-link]: TODO | ||
| [debug-test-suite-gsoc]: https://github.com/rust-lang/google-summer-of-code?tab=readme-ov-file#improve-rust-compiler-debuginfo-test-suite | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's probably implicit but would it make sense pointing out to whom the survey is targeted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that this sentence: "but it would also be useful to understand the current debugging struggles of Rust developers" states the target audience well enough. We also ask in the survey now if the respondents use Rust with other languages when debugging.