API for persistent tags or metadata on local and parameter variables

Aberta
#8,724 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
cpp

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
C++
Estrelas
1.3k
Forks
304
Merge médio
2d 20h
PRs com merge (30d)
10

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Vector35/binaryninja-api

Todas as issues de Vector35/binaryninja-api

Issues semelhantes

Mais issues de C++

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.