Vector35 / Vector35/binaryninja-api
Structured Type Editor
Nessuno ha ancora preso questa issue.
- Lingua principale
- C++
- Stelle
- 1.3k
- Fork
- 298
- Merge medio
- 5g 5h
- PR unite (30g)
- 19
Descrizione
In Binary Ninja the only way to edit types directly is through free-form text. Though this approach has many advantages there are also some disadvantages. The some of the disadvantages of this approach are as follows:
- C-syntax may not be well known by the user.
- C-syntax is incapable of expressing somethings that our type system can express such as:
- Structures with slack space
- Offset pointers
- Confidence
- CONTAINING_RECORD
- Function Parameters with specified storage
- (Register) Stack adjustments
- System Calls
Our current approach to the above is to add special extensions to the clang type parser to allow for these which works but requires users to understand new custom syntax.
To address these concerns we plan to devise a Structured Type Editor. This would allow users an alternative method for constructing types which would give users a more guided approach to creating structures as well as exposure of some features which aren't currently possible with the current free-form editor.
The idea would be to keep the existing interfaces as is, and augment them with a new alternative type editing interface.
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
No files, tests, or entry points are named. Start by reviewing the existing type-editing interfaces and the current clang type-parser extensions; the work is done when a defined structured editing interface covers the listed type-system features without changing existing interfaces.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- cpp
- 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
- 20/100