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
  • #4890
Closed
Open
Issue created Apr 30, 2021 by Derek Bruening@derekbrueningContributor

CURIOSITY on mmap failure reason

Running a proprietary app hits this assert:

<CURIOSITY : !fail || result == -9 || result == -13 || result == -22 || result == -26 || result == -11 || result == -12 || result == -19 || result == -14 || result == -1 in file core/drlibc/drlibc_unix.c line 121

Investigating shows that the mmap error code is -17 == EEXIST. This was not a possible error on old kernels which is likely why it's not on that list.

Assignee
Assign to
Time tracking