Missing API functions to distinguish user vs. auto

Aberta
#8,688 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
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
42/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
cpp
Domínio
api

Direção de pesquisa

Start by reviewing the listed BNSetAuto* and BNSetUser* API pairs and their corresponding getters in the public API. The issue does not identify files or tests, so first locate these declarations and implementations and check which properties lack a way to distinguish user from auto values. Done means adding query functions for the applicable properties so syncing tools can identify user changes; the issue leaves the full affected list for verification.

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

Descrição

What is the feature you'd like to have?
For many types of objects or properties, there are separate BNSetUserFoo and BNSetAutoFoo setters, suggesting that Binary Ninja tracks whether each instance of that object/property is user or auto, but there is no API function to query whether it's user or auto.

I'm requesting that such API functions be added.

Here is a table of affected objects/properties. Disclaimer: this table was compiled by AI and I didn't check every one, but I think it's accurate.

Auto setter User setter Getter
BNSetAutoCallTypeAdjustment BNSetUserCallTypeAdjustment BNGetCallTypeAdjustment
BNSetAutoCallStackAdjustment BNSetUserCallStackAdjustment BNGetCallStackAdjustment
BNSetAutoCallRegisterStackAdjustment BNSetUserCallRegisterStackAdjustment BNGetCallRegisterStackAdjustment
BNSetAutoCallRegisterStackAdjustmentForRegisterStack BNSetUserCallRegisterStackAdjustmentForRegisterStack BNGetCallRegisterStackAdjustmentForRegisterStack
BNSetAutoInstructionHighlight BNSetUserInstructionHighlight BNGetInstructionHighlight
BNSetAutoBasicBlockHighlight BNSetUserBasicBlockHighlight BNGetBasicBlockHighlight
n/a BNAddUserCodeReference
BNRemoveUserCodeReference
BNGetCodeReferencesFrom
BNAddDataReference
BNRemoveDataReference
BNAddUserDataReference
BNRemoveUserDataReference
BNGetDataReferencesFrom
n/a BNAddUserTypeReference
BNRemoveUserTypeReference
BNGetCodeReferencesForTypeFrom
n/a BNAddUserTypeFieldReference
BNRemoveUserTypeFieldReference
BNGetCodeReferencesForTypeFieldsFrom
BNSetAutoFunctionInlinedDuringAnalysis BNSetUserFunctionInlinedDuringAnalysis BNGetFunctionInlinedDuringAnalysis

Is your feature request related to a problem?
Just working on a custom syncing tool where I want to sync as much information as possible, but need to distinguish user changes (which should be synced) from auto changes (which shouldn't).

Are any alternative solutions acceptable?
It seems to me that the solution is pretty straightforward, but it's hard to say without seeing the BN codebase.

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.