Signal handling on `WindowsUserland`
Open
Nobody has claimed this yet.
target-windows
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
For now, we place dummy implementation at `PunchThrough` whenever Linux guest-side signal syscalls happen:
```rust
// in litebox_platform_windows_userland.rs:
PunchthroughSyscall::RtSigaction { .. } |
PunchthroughSyscall::RtSigprocmask { .. } => {
Ok(0)
}
```
Actual implementation to be added.
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 in litebox_platform_windows_userland.rs at the PunchthroughSyscall handling for RtSigaction and RtSigprocmask. Read the surrounding WindowsUserland signal and punchthrough code to determine the expected behavior for Linux guest-side signal syscalls. Done means replacing the dummy Ok(0) handling with an actual implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100