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
  • #5257
Closed
Open
Issue created Dec 17, 2021 by Abhinav Anil Sharma@abhinav92003Contributor

Include native run in some tests to verify kernel behaviour

For some tests, it makes sense to do a native run of the test app to make sure that the behaviour expected from the kernel (or other external entities emulated by DR) is correct. E.g. in linux.sigaction we have asserts that check the expected errno from the rt_sigprocmask syscall in various error scenaiors. It'll be good to verify that the kernel's behaviour hasn't changed by running the test app natively too, before running it under DR.

If we don't do the native run, we cannot be sure if what DR is doing is correct (e.g. returning EINVAL instead of EFAULT)

Assignee
Assign to
Time tracking