Skip to content

Expand debugging problem: Add further background to the documentation. #45

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.

Sign up for GitHub

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
Ajay-singh1 wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Expand debugging problem: Add further background to the documentation. #45

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c8207bb
docs: Add unresolved questions , further background and acceptance cr…
Ajay-singh1 Apr 4, 2026
f35dde0
Update debugging.md to remove incomplete sections
Ajay-singh1 Apr 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion problem-space/0005-debugging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,17 @@ TODO
## Further Background
[further-background]: #further-background

TODO
Modern debuggers rely on debug information formats such as DWARF (on Unix-like systems) and PDB (on Windows) to map compiled binaries back to source-level constructs.

Rust currently emits debug information that is largely compatible with existing tooling designed for C and C++. However, Rust’s language features—such as enums with rich semantics, pattern matching, and async/await transformations—do not always map cleanly onto these formats.

As a result, debuggers often fall back to displaying low-level representations of Rust types, exposing implementation details (e.g., discriminants and internal fields) rather than high-level abstractions.
Copy link
Copy Markdown
Collaborator

@teor2345 teor2345 Apr 6, 2026

Choose a reason for hiding this comment

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

How do you know this? Can you link to where you got this information from?

Copy link
Copy Markdown
Contributor Author

@Ajay-singh1 Ajay-singh1 Apr 7, 2026

Choose a reason for hiding this comment

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

https://rustc-dev-guide.rust-lang.org/debugging-support-in-rustc.html

Copy link
Copy Markdown
Contributor Author

@Ajay-singh1 Ajay-singh1 Apr 7, 2026

Choose a reason for hiding this comment

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

It is mentioned on the official documentation.


In mixed-language projects, these issues are amplified. C++ and Rust use different abstractions and conventions, and there is no unified model for representing types and execution flow across both languages in debugging tools.

Additionally, Rust’s async model introduces compiler-generated state machines, which can obscure control flow and make stack traces harder to interpret during debugging.
Copy link
Copy Markdown
Collaborator

@teor2345 teor2345 Apr 6, 2026

Choose a reason for hiding this comment

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

Again, this paragraph needs a reference to user experiences or other documentation of what works and what doesn't.

Copy link
Copy Markdown
Contributor Author

@Ajay-singh1 Ajay-singh1 Apr 7, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

I'll add a reference to this section of the documentation.


TODO: fill in the remainder of this section

## Experts & Champions
[experts--champions]: #experts--champions
Expand Down