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
  • Merge requests
  • !2565

i#2558: relax client reachability and vmm base location

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Derek Bruening requested to merge i2558-static-reachability into master Jul 25, 2017
  • Overview 2
  • Commits 5
  • Pipelines 0
  • Changes 11

Adds a new option -reachable_client, on by default. When turned off, client libraries being within 32-bit-displacement reachability of the code cache is relaxed, both the library load location and the fatal error on violation. This is particularly useful for statically-linked clients whose location is difficult to change.

Includes changes to vmm allocation required to make this work for statically-linked clients:

  • Eliminates the setting of heap reachability constraints prior to vmm allocation, except for -heap_in_lower_4GB which has no fallback.
  • Client libraries are now loaded after the vmm is allocated.
  • -vm_base_near_app tries to be near the app but on failure, if -vm_allow_not_at_base, it allows allocating away from the app.
  • When reserving any available memory, on UNIX, we take from the high end, for a lower chance of impacting the brk.

Adds a test of a static client with a large heap where the default -vm_base or being near the app fail.

Fixes #2558 (closed)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: i2558-static-reachability