How much work to get this to work with the WebAssembly format?
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
I'd love to step forward and reverse in web assembly code, any idea how much work would be required to make this work?
Contributor guide
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 reading rr's recording, replay, and reverse-execution documentation and identifying how WebAssembly code would enter the supported debugging path; define the required scope and a reproducible stepping scenario before estimating the work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100