Support for "catch syscall" or other means of breaking on system call entry and exit
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Right now attempting to catch a syscall during replay results in an error indicating that the feature is not supported. This means that the best a user can do is break execution on the libc wrappers that exist for some system calls. This workaround isn't sufficient for breaking on all system call entries and exits.
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 describes replay-time failure when attempting to catch a syscall and the limitation of using libc wrappers instead. No source files, tests, or entry points are identified; the work is complete when syscall entry and exit breakpoints are supported during replay without the current unsupported-feature error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100