Handle file open/close during experimental sessions
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Some Gecko debugging helpers dump data to named files. This would require support stdio open/write/close. At least open() would need to be explicitly allowed and executed. Maybe we should only allow open() to create a file that doesn't already exist, to avoid a replaying process accidentally damaging the file system.
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 source file, test, or entry point is identified. Start by tracing how stdio open, write, and close calls are handled during recording and replay, then resolve whether open() should be allowed only for creating nonexistent files. Done means experimental sessions can safely support the required file operations without replay damaging existing files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100