rust-lang / rust-lang/rustc_codegen_cranelift
Set prologue_end, epilogue_begin, basic_block and is_statement for .debug_line
Open
Nobody has claimed this yet.
A-debuginfo
C-enhancement
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 157
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 3
Description
This tells the debugger what good positions to place a breakpoint are.
https://docs.rs/gimli/0.20.0/gimli/write/struct.LineRow.html
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the gimli LineRow documentation linked in the issue, then trace where rustc_codegen_cranelift emits .debug_line data. Determine how prologue_end, epilogue_begin, basic_block, and is_statement should be populated; the work is done when the generated debug-line information contains the appropriate breakpoint-position flags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100