Register plugins for operands

Abierto
#665 0 comentarios 5 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
cpp
Área
reverse-engineering

Línea de trabajo

Start by reading PluginCommand and the existing instruction-level callbacks referenced in the issue. Trace how right-click context and InstructionTextToken data are exposed, then define what done means for registering a plugin on an operand and receiving that operand token plus its instruction address.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Component: Core Component: UI Effort: Low Impact: Medium UI: Linear

I think it would be nice to have a PluginCommand.register_for_operand that allowed a plugin to operate on a particular operand of an instruction. The plugin callback would be passed an InstructionTextToken object representing the operand that was right-clicked by the user (as well at least the address of the instruction it belongs to).

A very simple use case for this would be a plugin that would highlight all instructions that use a particular register. The user could right click a register, select the plugin, and then zoom out to see all instructions highlighted in a different color to indicate usage. This would be advantageous, because the token highlighting already provided by Binary Ninja can't be easily discerned when a function is zoomed out, but an entire line highlighted would be. Additionally, with the introduction of SSA, a plugin like this could apply highlighting to only instructions that use this particular version of the register, ignoring new definitions.

Obviously, the above example can be accomplished through the console, but that's not really the point, since it's just to demonstrate the usefulness of an operand-level plugin. With the current available callbacks, the user would have to select an instruction, invoke a plugin, and then plugin would then have to prompt the user to select the operand. This would streamline that process and make it a little more user friendly.

Lenguaje dominante
C++
Estrellas
1.3k
Forks
298
Merge medio
5 d 5 h
PR fusionados (30 d)
19

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Vector35/binaryninja-api

Todos los issues de Vector35/binaryninja-api

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.