Vector35 / Vector35/binaryninja-api
main function identification does not always jump to main function
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Version and Platform (required):
- Binary Ninja Version: 3.6.4799-dev, 8197e491
- OS: windows
- OS Version: 10
- CPU Architecture: x86_64
Bug Description:
I noticed that main function identification does not always jump to the main function. I can see from the logs that it found the main function, but does not navigates to it.
Steps To Reproduce:
- Load a x64 windows binary (I did not test other platforms)
- Make sure it finds the main function from the logs
- If it navigates to main function, reopen same binary until you trigger the issue
If this is not enough for reproducing the issue, I can share my binary.
Expected Behavior:
I expect BN to always navigate to the main function if it finds it.
Screenshots:
In the first log entry, it navigated to the main function that it found but in second entry it stayed on _start function.
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 issue with an x64 Windows binary, reopening it until main-function identification succeeds but navigation remains at _start. Compare the logs and navigation state for successful and failed runs. Done means the interface consistently navigates to the identified main function whenever detection succeeds.
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