rr-debugger / rr-debugger/rr

CPUID-triggered rcb undercounts are not reliably handled

Open
#1,262 43 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

... and then replay diverges :/. I've never seen this warning printed on my Ivy Bridge machine before, and IIRC this was a Haswell bug.

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 CPUID-triggered rcb undercount and replay divergence described in the issue, comparing behavior on Ivy Bridge and Haswell. Locate rr's CPUID handling and rcb accounting, then use the replay result and warning behavior as the completion criteria; the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools, reverse-engineering
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.