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
  • #4618
Closed
Open
Issue created Dec 15, 2020 by Derek Bruening@derekbrueningContributor

common.decode, common.decode-stress, and client.cleancall tests silently die after their nth fault on Server2016

decode and decode-stress: output just ends:

2020-12-05T20:33:13.7774875Z 12: Testing far call/jmp
2020-12-05T20:33:13.7775258Z 12: Bad instruction, instance 3

Similarly for cleancall:

2020-12-05T20:34:14.4096097Z in restore_state for our clean call crash 1
2020-12-05T20:34:14.4096607Z Access violation, instance 1

Yet decode-bad works, and earlier faults work: so clearly faults in general are working. Not clear what is happening.

Assignee
Assign to
Time tracking