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

drreg ever_spilled state never reset on new block

Xref #3821 (closed) Xref https://github.com/DynamoRIO/dynamorio/pull/3822#discussion_r322862007

drreg's per-reg ever_spilled state does not seem to be reset, ever. It seems like it should be set to false at the start of a new block, in drreg_event_bb_analysis next to where app_uses=0 or sthg like that. It also seems like failing to reset it might affect restores: though maybe not in common use patterns since there's other state that controls restores, so maybe there are no consequence to this. This issue covers investigating further and fixing.

Assignee
Assign to
Time tracking