Vector35 / Vector35/binaryninja-api
Type propagation to DataVariables
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Binary Ninja could do a better job inferring DataVariable types. The primary reason we don't propagate types from analysis to DataVariables is that the DataVariable could be shared amongst multiple functions. Analysis would have to take into account all function which reference the DataVariable in order to make correct assumptions about a DataVariables type. We'd essentially have to wait until all analysis has settled and then go through references to each of these as a second pass.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by mapping how analysis references DataVariables and where analysis completion is represented; the issue names no files, tests, or entry points. Determine how a second pass could consider all function references after analysis settles, and define completion as correct type propagation for shared DataVariables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100