rr-debugger / rr-debugger/rr

`rr replay` fails with errno: 0 'Success'

Open
#1,589 5 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

rharwood@gssproxy:~/gssproxy/proxy$ rr replay
[FATAL /home/rharwood/rr/src/Event.cc:75:Event() errno: 0 'Success'] 
 -> Unexpected event [FATAL /home/rharwood/rr/src/Event.cc:340:type_name() errno: 0 'Success'] 
 -> Unknown event type 31
rharwood@gssproxy:~/gssproxy/proxy$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux testing (stretch)
Release:    testing
Codename:   stretch
rharwood@gssproxy:~/gssproxy/proxy$ 

Please let me know if there is any more information I can provide. Thanks!

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

Reproduce rr replay using the reported Debian testing environment and inspect the failure path at Event.cc:75 and Event.cc:340. Trace how event type 31 is recorded and decoded, then verify that replay handles the event without aborting and add or update focused coverage if the relevant test location can be found.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
devtools
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.