Asynchronous exception-class signals are not properly handled
Open
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
LiteBox currently treats some asynchronous exception-class signals (e.g., `SIGSEGV`) as synchronous hardware exceptions when they interrupt guest execution. One consequence of this problem is the bug that PR #1191 has fixed.
Contributor guide
Research direction
Start by tracing LiteBox's handling of asynchronous exception-class signals, using PR #1191 as the available reference for the related fix. The work is done when signals such as SIGSEGV are no longer treated as synchronous hardware exceptions while interrupting guest execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100