Vector35 / Vector35/binaryninja-api
flow-based highlighting
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
We'd like the ability to change the way selection highlighting works beyond strict text matching. One such enhancement is already tracked in #321.
Another highlighting mechanism which would likely become the default is flow-based highlighting that would use information from SSA and other ILs to highlight registers or stack values based on common storage of a variable. This would also prevent necessary highlighting where a register is reallocated to a different use later in a function.
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 reviewing issue #321 and the current strict text-matching selection behavior. Investigate how SSA and other ILs represent shared variable storage, then define flow-based highlighting for registers and stack values, including the case where a register is later reallocated to another use; no files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100