Vector35 / Vector35/binaryninja-api
Large function is sliced into multiple functions unexpectedly
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Version: 5.2.8722
Sample: universal forge views programmatically
Function: 0x1000596a0
This function should end at 100083A3B, however Binja has sliced it a couple of functions, such as 1000696a2. Function 0x100017c60 has the same issue.
Reported to us by a user on Slack.
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 reproducing the report with the universal forge views programmatically sample in Binary Ninja 5.2.8722, examining functions 0x1000596a0 and 0x100017c60 and the reported boundary near 0x100083A3B. Trace the function-slicing behavior and identify why 0x1000696a2 is separated; done means both affected functions retain the intended boundaries without regressing related analysis.
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
- 38/100