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
  • #5705
Closed
Open
Issue created Oct 25, 2022 by Derek Bruening@derekbrueningContributor

Failure to encode rseq region that writes SP on aarch64

An app with an rseq region that writes SP crashes in release build and in debug it hits:

<Attached to 516 threads in application xxx (1000286)>
<Internal Error: Failed to encode instruction: 'str    %sp -> +0x0660(%x0)[8byte]'
>
<dropping 3rd pending alarm signal>
<Application xxx (1000286).  Internal Error: DynamoRIO debug check failure: core/emit.c:363 pc != NULL

The culprit is the rseq mangling register snapshot code which treats SP like a GPR and tries to store and load from and to it.

Assignee
Assign to
Time tracking