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
  • #3507
Closed
Open
Issue created Apr 04, 2019 by Derek Bruening@derekbrueningContributor

better support for from-OS large heap and cache allocations

I was experimenting with using large allocations from the OS instead of DR's -vm_reserve and hit several issues with the current runtime options which I plan to fix:

  • allow -no_vm_reserve to work Today get an assert: core/heap.c:1034 vmcode_get_start() >= heap_allowable_region_start

  • don't make me set trace unit sizes to be bigger than -cache_commit_increment when I have -disable_traces

  • let me raise -heap_commit_increment larger than signal special heap unit size w/o having to raise -max_pending_signals to some ridiculous amount

Assignee
Assign to
Time tracking