rr-debugger / rr-debugger/rr

Recording FF crashtest-ipc: "Should be entering mmap2, but instead at clone"

Open
#1,119 1 comment 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

Assertion `t->regs().orig_eax == syscallno' failed to hold. Should be entering mmap2, but instead at clone

I've seen this happen twice now with gecko-dev sha1 876943a61001e8ccf48ce6cfb9cd0724100b0bb8. This is at the very end of the recording session, so it's not going to cause significant issues in practice, so not blocking 1.3 on it.

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 crashtest-ipc recording failure with gecko-dev at sha1 876943a61001e8ccf48ce6cfb9cd0724100b0bb8. Investigate the assertion that expects mmap2 but observes clone near the end of recording, then verify that the recording completes without the assertion.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.