Catch replay divergence early in heavily syscall buffered code
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
I'm debugging some code where there appears to be a replay divergence in a region of code that is heavily syscall buffered. I think it would be useful to have the syscallbuf library check rec->syscallno against the actual syscallno it's about to execute and fail early if it sees a divergence.
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 locating the syscallbuf library and the code that executes buffered syscalls, then inspect how rec->syscallno is used. The change is done when the recorded syscall number is checked against the syscall about to execute and divergence fails early, with relevant coverage added if the existing tests support it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100