Crash on replay (`SYSCALLBUF_FLUSH: expecting tracee signal or trap, but instead at 'fork'`)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
The project is awesome. Unfortunately, it crashes when I try to replay the recorded dump of our system (we have all sorts of syscalls, heavy disk and network I/O, shared memory, parallelism and stuff). I wish I could debug the problem and contribute to the project, but I lack the knowledge of the Linux kernel stuff needed to do that.
What books/blogs/otherwise literature on Linux system programming you could suggest to make sense of the internals of rr-debugger for newcomers?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; begin by reviewing the request for newcomer-oriented Linux system-programming resources and rr internals. A useful outcome would need a defined documentation scope and a curated set of resources that helps newcomers understand rr. The long-unanswered thread should be checked before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100