Missing API functions to distinguish user vs. auto

Ouverte
#8,688 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
42/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
cpp
Domaine
api

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
C++
Étoiles
1.3k
Forks
304
Merge moyen
2 j 20 h
PR mergées (30 j)
10

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Vector35/binaryninja-api

Toutes les issues de Vector35/binaryninja-api

Issues similaires

Plus d'issues C++

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.