Divergence involving socket ioctls
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Spun off from #1571.
The events before the problematic socketcall is executed: https://gist.github.com/DarkPlayer/147f8f3f20cd4a2c8f35
The dump belongs to:
[FATAL /home/michael/projects/rr/src/ReplaySession.cc:837:check_ticks_consistency() errno: 0 'Success']
(task 27207 (rec:27070) at time 2888468)
-> Assertion `llabs(ticks_now - trace_ticks) <= ticks_slack' failed to hold. ticks mismatch for 'SYSCALL: socketcall'; expected 291893881, got 291893891
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 ReplaySession.cc at check_ticks_consistency(), then review the recorded events in the linked gist around the socketcall. Investigate the reported 10-tick mismatch involving socket ioctls and determine whether it can be reproduced. Done means the socketcall replay no longer triggers the ticks-consistency assertion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- operating-systems, reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100