Improve non-interactive debugging
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Most (all?) of the rr issues I report are found while running rr in non-interactive mode. These issues occur in automation and locally when using our tools that automate running Firefox and rr. Trying to reproduce these issues without using these tools can be difficult (sometimes impossible?) and time consuming.
To help both reporting and debugging these issues it would great if there was a way to dump helpful/required debug data to a log file while in non-interactive mode.
Perhaps a log file which is populated when there are fatal errors/assertions? Providing the file path via a command ling flag would be helpful for automation. Note using stderr is a pain when running in automation because the logs get mixed with the application that is running,
What do you think?
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
No files, tests, or entry points are named. Start by examining how rr handles fatal errors and assertions in non-interactive mode, including its command-line parsing and current stderr output. Done means defining and implementing a supported log-file option whose output remains useful for automated debugging without mixing with the application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100