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
  • #5304
Closed
Open
Issue created Jan 28, 2022 by Derek Bruening@derekbrueningContributor

instr_is_encoding_possible fails on unreachable pc-relative operands but takes no target

While adding a test for #5302 (closed) on arm, I hit this:

ASSERT FAILURE: /home/derek/dr/git/src/suite/tests/api/ir_arm.c:80: instr_is_encoding_possible(instr)

This is for the instruction in test_pcrel() in ir_arm.c.

The problem is that instr_is_encoding_possible() does not take in a target location for encoding, so it can't know whether pc-relative operands will reach. It has to relax those reachability checks.

Assignee
Assign to
Time tracking