API for persistent tags or metadata on local and parameter variables

Abierto
#8,724 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

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
Activo
Stack tecnológico
cpp

Línea de trabajo

Start by reading the public API definitions and documentation for variables, BinaryView metadata, and tags to see how variable identities are represented and persisted. The issue does not name specific files or tests; trace the relevant API entry points and existing persistence tests. Done means plugins can attach, retrieve, and remove persistent metadata on local and parameter variables, with documented behavior when reanalysis changes variables.

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

Descripción

What is the feature you'd like to have?

An API to attach, retrieve, and remove persistent annotations on individual local and parameter variables. A string value would be sufficient, including a JSON string for structured information. The annotations should survive saving and reopening the BNDB.

Native variable tags would be useful, but arbitrary per-variable metadata would also meet my needs.

Is your feature request related to a problem?

I’m building analysis tooling that recovers variable names and types. I’d like to record why I’m confident, or uncertain, that a particular local or parameter is correctly named or typed, including the source of that information and supporting evidence.

Function-level tags are too coarse, and address tags annotate an instruction rather than the variable itself. Putting this information into variable names would clutter the analysis.

Are any alternative solutions acceptable?

Yes. An officially supported way to associate persistent metadata with a variable would be sufficient; it doesn’t have to use the existing tag system.

BinaryView-level metadata with a custom variable-keying scheme is a possible workaround, but it leaves plugins responsible for maintaining the association as variables change during analysis.

Additional Information:

For example, an annotation could contain:

{
  "property": "type",
  "confidence": "tentative",
  "source": "analysis-plugin",
  "reason": "Matches observed field accesses; not independently verified"
}

This is explanatory metadata, separate from Binary Ninja’s existing analysis-confidence values. Documented behavior when variables are split, merged, or removed during reanalysis would also be helpful.

Lenguaje dominante
C++
Estrellas
1.3k
Forks
304
Merge medio
2 d 20 h
PR fusionados (30 d)
10

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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.