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
  • #3160
Closed
Open
Issue created Sep 11, 2018 by Derek Bruening@derekbrueningContributor

Add full-state-checking detach tests

In light of bugs like #3116 (closed), we should add detach tests that explicitly check that every piece of state is properly restored: every register, segment state, signal state. The current detach tests just ensure that execution continues without crashing, but we could mess up several registers and not crash these simple test apps.

For #3116 (closed) I am adding some signal state testing to existing detach tests. This issue covers writing new tests with threads that place specific values into each register and segment and check that they are restored.

Assignee
Assign to
Time tracking