rust-lang / rust-lang/backtrace-rs
Support printing DSO context when symbols aren't avaliable
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 628
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
Currently backtraces don't print enough context when symbols aren't resolved in-process (for whatever reason). If someone wants to attempt symbolising out of process then it may be impossible from the backtrace alone.
Quoting @bjorn3:
To be able to actually symbolize the backtraces this would need to print both the path of the DSO (executable or dylib) and the offset within this DSO. It could be a dylib loaded at runtime and thanks to ASLR the exact location of DSOs can't be determined anymore after the fact unless we print it here.
This could take inspiration on what backtrace-rs does on Fuchsia which unconditionally does backtrace symbolication out of process.
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 by reading the issue discussion and examining how backtrace-rs handles out-of-process symbolication on Fuchsia, which the report cites as inspiration. Identify the backtrace output path that handles unresolved symbols; done means the output includes each DSO's path and offset so it can be symbolized after the process exits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100