Vector35 / Vector35/binaryninja-api
Identification of static DataVariables
Open
Nobody has claimed this yet.
Component: Core
Effort: Low
Impact: Medium
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Is your feature request related to a problem? Please describe.
DataVariables which are only referenced from a single function should reasonably be labeled as static. Their definition could then be shown within the function which references them.
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
The issue names no file, test, or entry point. Begin by locating DataVariable handling and the logic that determines whether a variable is static; completion means single-function references are labeled static and their definitions can be shown within the referencing function.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100