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
  • #630
Closed
Open
Issue created Nov 28, 2014 by Derek Bruening@derekbrueningContributor

if dynamorio base conflicts w/ app or before-DR library base => fatal reachability problem

From bruen...@google.com on December 02, 2011 14:24:58

pasting from a problem raised over email:

Most likely firefox has a library that it loads at or overlapping the DR lib preferred base of 0x0000000071000000.

As a workaround you can reconfigure with something like this (adjust the value to avoid firefox libs, but keep it in the lower 2GB):

cmake -Dpreferred_base=0x61000000 .

And then rebuild.

Long-term we will have DR loaded by our loader (right now the client and its libs are but not DR) and this problem will go away. It was never high enough priority to tackle in the past: this is the first we've heard of a conflict.

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=630

Assignee
Assign to
Time tracking