rr-debugger / rr-debugger/rr

Warning: Syscall `clock_gettime' not handled during experimental session.

Open
#1,233 4 comments 0 reactions 0 assignees View on GitHub

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 every time I call nsFrame::PrintDisplayList from the debugger.

No big deal, since everything continues to work just fine, but we could probably suppress this warning by handling clock_gettime in some way. It would probably be fine to just execute the system call.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the warning when calling nsFrame::PrintDisplayList from the debugger during an experimental session, then trace where rr reports unhandled clock_gettime syscalls. Confirm the syscall can be handled without affecting replay, and verify that the warning no longer appears while existing behavior remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
devtools, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.