hyperlight-dev / hyperlight-dev/hyperlight-wasm
Make sure that wasmtime gets all the traps it needs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 728
- Forks
- 39
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 23
Description
Currently, we only properly call the trap handler given to wasmtime_init_traps() when an undefined instruction is executed. #113 should ensure that trapping accesses to virtual memory are also handed to the trap handler, but there are probably some other exceptions (e.g. floating point) which need to be handed to wasmtime. We should figure out what all of them are and make sure they are properly sent to wasmtime.
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
Start by reviewing wasmtime_init_traps() and the changes proposed in issue #113. Identify which exception classes are currently handled and determine the complete set that must reach Wasmtime's trap handler. Done means all required traps, including cases beyond undefined instructions and virtual-memory accesses, are routed correctly and covered by verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- compilers, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100