Missing API functions to distinguish user vs. auto

Aperta
#8,688 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp
Ambito
api

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
C++
Stelle
1.3k
Fork
304
Merge medio
2g 20h
PR unite (30g)
10

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Vector35/binaryninja-api

Tutte le issue di Vector35/binaryninja-api

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.