Skip to content

feat: Add the 2026 Debugging survey report - #407

Draft
hashcatHitman wants to merge 26 commits into
rust-lang:mainfrom
hashcatHitman:debugging-2026-report
Draft

feat: Add the 2026 Debugging survey report#407
hashcatHitman wants to merge 26 commits into
rust-lang:mainfrom
hashcatHitman:debugging-2026-report

Conversation

@hashcatHitman

Copy link
Copy Markdown
Member

This is a first draft. I think it's pretty good so far, but there are questions that need answering still. Please see the comments starting with TODO:.

@Kobzol Kobzol left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much for working on this! I left a few comments.

It's a good start definitely, and I know that it takes a lot of time to go through the questions and prepare the charts. As a follow-up, I think we can add a few more charts, maybe even some cross-correlated charts, as suggested, and then of course write a blog post. Are you up for it? :)

Comment thread surveys/2026/debugging/report/main.py Outdated
Comment thread surveys/2026/debugging/report/main.py Outdated
Comment thread surveys/2026/debugging/report/main.py Outdated
Comment thread surveys/2026/debugging/report/main.py
Comment thread surveys/2026/debugging/report/main.py Outdated
Comment thread surveys/2026/debugging/report/main.py Outdated
}
debugger_used_for = "What are you using debuggers for?"
report.add_bar_chart(
"what-are-you-using-debuggers-for",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be nice to show a chart of this separated by the used tool(s). E.g. GDB, ...

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added two charts for this in 8257fd5. Let me know what you think?

Comment thread surveys/2026/debugging/report/main.py Outdated
Comment thread surveys/2026/debugging/report/main.py
Comment thread surveys/2026/debugging/report/main.py Outdated
This is a first draft. I think it's pretty good so far, but there are
questions that need answering still.

Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
In my copy-pasting, I missed a spot. Oops.

Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
I missed this one.

Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
@hashcatHitman
hashcatHitman force-pushed the debugging-2026-report branch from 4809560 to 97dd7af Compare April 15, 2026 01:31
Comment thread surveys/2026/debugging/report/main.py Outdated
Comment on lines +389 to +394
# multiple. I want to better represent information such as:
# - Of all responses, X% of users use the specific combo "Debugger" + "OS"
# - Of all responses for "Debugger", X% of users did so on "OS"
# - Of all responses for "Debugger", X% of users selected more than one "OS"
# - Of all responses for "OS", X% of users used "Debugger"
# - Of all responses for "OS", X% of users selected more than one "Debugger"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Possibly all these answers can be better explained in the blog post. These charts are slightly unwieldly and not very flexible for nuances. I am not sure but I would probably not think too much about the graph representation here.

db.open_answers(std_lib_pain),
)

visualizer_attribute_known = "If you are a library author, are you aware of and using the debugger visualizer attribute?"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The replies about the debugger visualizer are interesting, many don't know this tool (me included!); it could be useful to explain that in the blog post

Comment thread surveys/2026/debugging/report/main.py Outdated
@apiraino

Copy link
Copy Markdown
Contributor

Nice work, thanks @hashcatHitman, I see a couple of interesting findings.

One additional general observation after looking at the PDF: I feel that these wordclouds don't add a great deal of meaningful info. But if you find them interesting, it's fine to leave them there.

Kobzol and others added 12 commits July 1, 2026 18:56
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
I'm honestly not sure if these reveal anything interesting, but I'm glad
to have figured out how to make them.

Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
We can handle answers ending in periods now, so patching the dataframe
directly isn't needed for this anymore.

Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
@Kobzol

Kobzol commented Jul 12, 2026

Copy link
Copy Markdown
Member

If we decide to use the What are you using debuggers for? in the blog post, we would have to carefully explain how these were created, as it's quite complex 😆 Thank you for creating them though.

Thanks a lot for polishing the charts! I think that we have interesting data there, and it's time to move on to the blog post. Feel free to chat with me on Zulip to discuss it :) I think that it might be nice to structure it in a similar way as the previous similar survey that we did about compiler performance, where we split the conversation into several subtopics that were indexed at the top of the post.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants