Bitfield resolution in MLIL/HLIL

Abierto
#7,533 1 comentario 8 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
compilers, reverse-engineering

Línea de trabajo

Start by reading the MLIL/HLIL bitfield examples in the issue and the referenced binary, then review issue 694's discussion of bitfields in the type system. Determine how resolved bitfield accesses should appear in HLIL and whether the first accessed member should be hidden or represented anonymously. Done means the examples show the actual bitfield accesses without requiring manual arithmetic.

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

Descripción

Core: HLIL Core: MLIL Effort: High Impact: Medium UI: Linear

What is the feature you'd like to have?
I would like to see resolved accesses to bitfields in HLIL, since we now can express them (bitfields) in our type system.

Is your feature request related to a problem?
Currently you must do math in your head to determine the accessed bitfield, for example:

Image

The above is setting the first member a to 1 and 4 respectively for each structure.

Another, more annotated example:

MLIL listing:
Image

Types:
Image

Additional Information:
We also likely want to stop showing the first member being accessed, e.g. a in the examples above, and show either no access (the structure itself is loaded into the register) or some anonymous access, so that users do not get confused as to what is really getting accessed.

The above binary is available with: echo nebula rises persistently

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.