Vector35 / Vector35/binaryninja-api
Smarter Analysis Limits
Open
Nobody has claimed this yet.
Component: Core
Effort: Medium
Impact: High
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
- Tag functions that trigger analysis limits with the reason they were canceled.
- Don't trigger analysis limits on User Functions
- Don't trigger analysis limits on functions created from Debug Sources
- Don't trigger analysis limits on "high confidence" functions - recursive decent, very high confidence linear sweep functions
Possibly add another analysis phase where we go back and analyze functions that triggered certain limits, eg. functions that exceeded the maximum analysis time.
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
No files or tests are named. Start by tracing where analysis limits are applied to functions, then review the User Functions, Debug Sources, recursive descent, and high-confidence linear sweep cases. Done means canceled-limit reasons are tagged, the listed function categories are exempted appropriately, and any additional analysis phase has defined behavior.
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