Vector35 / Vector35/binaryninja-api
Reopening BNDB triggers analysis update
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
This bug was introduced in 3.5.4437-dev
Steps To Reproduce:
- Open a BNDB created with the same version
- See analysis happening
Expected Behavior:
Reanalysis shouldn't happen
Screenshots:
If applicable, please add screenshots here to help explain your problem.
Additional Information:
A binary that took 6 minutes for initial analysis has ~45 seconds of reanalysis after opening the bndb.
This doesn't happen in 3.4.4271.
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
Reproduce the issue by opening a BNDB created with the same version, comparing behavior between 3.5.4437-dev and 3.4.4271. Trace the BNDB reopening and analysis-update path to determine why reanalysis starts. Done means reopening a same-version BNDB no longer triggers reanalysis while initial analysis still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100