Assertion `ticks_now == trace_ticks' failed to hold
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
I get this error and don't know rr enough to see what is going wrong.
[FATAL ReplaySession.cc:840:check_ticks_consistency() errno: SUCCESS](task 7646 %28rec:6129%29 at time 45583)
-> Assertion `ticks_now == trace_ticks' failed to hold. ticks mismatch for 'SYSCALL: munmap'; expected 4306038, got 4306037
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 at ReplaySession.cc:840 in check_ticks_consistency() and inspect the reported SYSCALL: munmap mismatch. Use the record and replay context from the report, including task 7646 and time 45583, to investigate why expected and observed ticks differ. Done means identifying and correcting the cause, but the issue provides no reproduction steps or test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100