Handling of scratch-needed-but-not-allowed syscalls is poor
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Nonexistent?
This popped up in the context of #16: valgrind is doing a sigtimedwait from a context that can't use scratch (which I need to poke at more), and the code to process the syscall outparams doesn't handle the scratch-aborted case.
The naive fixes for this are messy and verbose. I'm going to paper over the valgrind issue and leave this open for a cleaner general solution, if one exists.
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 with the context in issue #16 and inspect how syscall outparams are processed when scratch use is unavailable. Investigate the valgrind sigtimedwait case and the scratch-aborted path. Done means a general solution handles these outparams cleanly without relying on the mentioned paper-over.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- operating-systems, reverse-engineering
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100