It is too hard to find the various gdb commands available when doing rr replay
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
There is no obvious way (i.e. I clicked around on the web page and the github project for more than ten minutes) to find the various gdb commands that are available when running rr replay.
In this particular case I wanted to find the way to avoid debugee standard error from being shown when replaying. I know there is a way, I just cannot remember how I did last time and now I cannot find anything.
What I would expect is a nice little table with all the commands (perhaps even with useful abbreviations) summarizing what rr-specific things are available in gdb.
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
Start by reviewing the rr replay documentation and the GDB command entry points referenced by the project; no specific files or tests are named in the issue. Inventory the rr-specific commands and useful abbreviations, including the stderr-related command, in a discoverable table, and verify that a user can find the table from the project documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100