rust-lang / rust-lang/backtrace-rs
`backtrace::resolve` can cause UB under Miri
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 628
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
Calling backtrace::resolve with invalid addresses causes UB in the Miri specific path. backtrace::resolve is supposed to be safe, so this UB would be a false positive.
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 locating the Miri-specific path used by backtrace::resolve and inspect how invalid addresses are handled. Reproduce the issue under Miri with invalid addresses; done means the safe API no longer produces undefined behavior or a Miri false positive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100