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
  • #4315
Closed
Open
Issue created Jun 04, 2020 by Derek Bruening@derekbrueningContributor

Add handling for restartable sequence corner cases

This covers handling some corner cases for restartable sequences ("rseq") which our original implementation for #2350 (closed) does not handle. These are from the list at https://github.com/DynamoRIO/dynamorio/issues/2350#issuecomment-532401625

There are a number of corner cases left to cover, but they are lower priority. These are things like:

  • Invoking the 2nd execution on a sequence midpoint exit (maybe leveraging __rseq_exit_point_array)
  • Handling indirect branch exits out of a sequence
  • Remove the -rseq_assume_call option once we're satisfied we'll never go back to it
  • Add more sanity checks for existing requirements/assumptions
Assignee
Assign to
Time tracking