Improve unit tests in shim
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
After adding the support for separate stacks, the trick for unwinding stack, and fs/gs switch, the shim cannot directly make syscalls to the platform but goes through the `syscall_callback` entry. An advantage of having unit tests in the shim layer is that we don't need to repeatedly add a test on all platforms. We should revisit this in the future.
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 reading the shim layer around the `syscall_callback` entry and the existing handling for separate stacks, stack unwinding, and fs/gs switching. Identify which shim behaviors lack unit coverage and define the test cases needed to exercise them without platform-specific additions. Done means the relevant shim paths are covered by unit tests and the tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100