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
  • #1978
Closed
Open
Issue created Jul 21, 2016 by Administrator@rootContributor

spurious rep/repne prefix on BND JMPQ

Created by: algr

Running Ubuntu 16.04 LTS on Skylake. Any use of drrun warns with

<spurious rep/repne prefix @0x00007f57947207f8 (f2 41 ff e3): >

This is BND JMPQ which was added to ld.so as per https://gcc.gnu.org/ml/gcc/2014-01/msg00151.html

This is similar to #1899 (closed) but the fix for that tested for instructions of these categories:

info->type != OP_call && info->type != OP_call_ind && info->type != OP_ret && info->type != OP_jmp && info->type != OP_jmp_short &&

while this one is OP_jmp_ind. This test ought to be factored out into a robust self-contained test. There are similar tests in instr.c but not directly on opcodes, they expect an instr, but only use its opcode.

Assignee
Assign to
Time tracking