Backtrace: Display binary offset
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 504
- Forks
- 37
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 44
Description
We should provide a way to map a Pc to its binary offset in the source module level for a better understanding of where the program crashed. Additionaly we need this mapping for future debugging support as DWARF information don't know Pc.
For now, all single "trappable" VM instruction corresponds to a single Wasm-level instruction (no unified instructions nor pseudo trappable VM instruction), so a Pc (at trappable instruction) -> BinaryOffset is injective.
We need to figure out how to build an address map function efficiently.
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
The issue names no files, tests, or entry points. Start by locating the representations of Pc, BinaryOffset, trappable VM instructions, and DWARF information, then determine where an efficient address map belongs. Done means a trappable Pc maps to its source-module BinaryOffset for future debugging support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift, wasm
- Domain
- compilers, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100