Vector35 / Vector35/binaryninja-api
better differentiation of symbol origin
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Whether implemented via better provenance, or strong/weak typing, or some other method, it would be nice to be able to more easily differentiate auto sub_ and j_ and similar functions from others that are from symbols versus user generated. There's some facility using .auto on the symbol currently, or the symbol.type but this could use some improvement.
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 the existing symbol API's .auto facility and symbol.type behavior. Determine how symbol provenance is currently represented and what distinction the issue requires between automatically generated and user-generated functions; done means the API offers a clear, documented way to make that distinction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100