rr-debugger / rr-debugger/rr

assertion failure: Replay got unrecorded signal SIGSEGV (expecting SIGILL)

Open
#2,809 14 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

The full crash session: https://gist.github.com/bjorn3/3b7dc412becb7736486b52a370d4a67f

The pack: rr_crash.zip

This issue is deterministic. The executable uses Intel Process Tracing but due to the bug I was trying to debug using rr it crashes way before PT is started. In fact it crashes before main inside a .init_array initializer.

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 deterministic failure with rr_crash.zip and reviewing the linked full crash session. Focus on the crash before main, during the .init_array initializer, and before Intel Process Tracing starts. Done means replay no longer reports an unrecorded SIGSEGV when SIGILL is expected.

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.