Vector35 / Vector35/binaryninja-api
Type resolution should consider subtype relationships
Nessuno ha ancora preso questa issue.
- Lingua principale
- C++
- Stelle
- 1.3k
- Fork
- 298
- Merge medio
- 5g 5h
- PR unite (30g)
- 19
Descrizione
What is the feature you'd like to have?
When resolving the types of variables within a function, subtyping relationships could be used in addition to confidence when type propagation has multiple options for the type of a variable. This may be as simple as always selecting the derived type if the options are a supertype and subtype. It could be a lot more nuanced than that.
Is your feature request related to a problem?
https://github.com/Vector35/binaryninja-api/issues/7367 - In the case presented in that issue, MyClass could be considered a subtype of id. That would ideally result in it being preferred as the local variable type over the less specific id. In practice this will also require additional work on the Objective-C side to ensure that MyClass / NSObject / objc_object have the appropriate subtype relationships.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Start by reviewing the type-resolution behavior described here and the related Binary Ninja issue 7367, focusing on how variable types are propagated when multiple options exist. Define how subtype relationships should interact with confidence, then verify that derived types are preferred over supertypes and that the Objective-C relationships among MyClass, NSObject, and objc_object are handled appropriately.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- cpp, objective-c
- Ambito
- reverse-engineering
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100