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
  • #2571
Closed
Open
Issue created Jul 28, 2017 by Administrator@rootContributor

vmarea and heap exit flags not reset on re-init

Created by: s-kanev

This came up in the following case:

  • static attach with a client (drmemtrace), which detaches with dr_app_stop_and_cleanup().
  • later, from the same process, invoke raw2trace_t, which uses dr_init_standalone() to map modules and decode instructions. Mapping modules then fails because update_dynamo_areas_on_release() doesn't remove VM areas thinking it's exiting, because both vm_areas_exited and heap_exiting are still set.

The fix is simple, don't statically initialize them, but use the proper _init() functions.

Assignee
Assign to
Time tracking