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
  • #3645
Closed
Open
Issue created May 24, 2019 by Derek Bruening@derekbrueningContributor

Pending reset lasts across detach and causes a reset even when disabled

If I use the dr_app* interface to launch DR, allocate a lot of memory or sthg and cause schedule_reset() to be called, then detach without taking over execution, then disable resets, and then re-attach and start executing, the first dispatch entry will go and do a reset even though they're disabled.

Action items:

  • Have a release-build check for reset being enabled and bail if so in both schedule_reset() and fcache_reset_all_caches_proactively().
  • Clear reset_pending in detach.
Assignee
Assign to
Time tracking