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
  • #2509
Closed
Open
Issue created Jul 07, 2017 by Al Grant@algrant-arm

Segmentation fault in some clients with __clear_cache

On AArch64 some dynamic code operations cause a crash in (or with) clients:

#include <stdlib.h>
int main(void) {
    void *page;
    posix_memalign(&page, 4096, 4096);
    __builtin___clear_cache(page, (char*)page + 4096);
    return 0;
}

this gets a segmentation fault with simple clients like libbbcount and libopcodes. The debug build says

<Application tried to execute from unreadable memory 0x0000000000000000.

We know DR on AArch64 traps IC IVAU in order to handle dynamic code, so maybe there's some interaction between that and the instrumentation that these clients are putting in.

Assignee
Assign to
Time tracking