spinframework / spinframework/spin
Investigate current state of guest debugging
Open
Nobody has claimed this yet.
area/runtime
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
Reportedly, wasmtime guest debugging has improved significantly over the past months. We should evaluate it for Spin and - if it's useful enough - consider enabling debug_info either by default or via spin up flag and documenting how to get it working for supported languages.
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 evaluating current Wasmtime guest-debugging support for Spin, focusing on the linked debug_info configuration and the spin up entry point. Determine whether debugging is useful enough to enable by default or expose as a flag, and document how to use it for supported languages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100