Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dynamorio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,467
    • Issues 1,467
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • DynamoRIO
  • dynamorio
  • Issues
  • #5221
Closed
Open
Issue created Nov 19, 2021 by Abhinav Anil Sharma@abhinav92003Contributor

Undo pre-syscall actions in case of failure

For some syscalls DR does complex pre-syscall handling (like clone, clone3,...) in core/unix/os.c. If these syscalls fail, we should ensure that we undo pre-syscall stuff if needed.

For clone3, we handle the case where we know it will return ENOSYS by detecting whether the system supports clone3 or not during init time, and skipping the pre-syscall stuff if we see a clone3 later. This issue is to track handling of other error scenarios and other such syscalls.

Assignee
Assign to
Time tracking