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
  • #3316
Closed
Open
Issue created Dec 17, 2018 by Derek Bruening@derekbrueningContributor

support using an external allocator for standalone mode

When using DR in standalone mode, it may be best to use an external, regular heap allocator, rather than DR's custom allocator, for several reasons:

  • Better performance: DR standalone mode is not using per-thread dcontexts, meaning all allocations are global and using a global lock.

  • Tool support: sanitizers like ThreadSanitizer do not recognize DR's allocator or its locks, leading to false positive reports

  • Scalability: xref #3296 (closed), which is now solved.

Assignee
Assign to
Time tracking