Vector35 / Vector35/binaryninja-api
improve documentation for large binaries
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
While #4684 added https://dev-docs.binary.ninja/guide/troubleshooting.html#working-with-large-or-complex-binaries we need to flesh that out with either more details, a youtube video, maybe a blog post or some other workflow showing how we handled a specific binary. Additionally, we probably need to include more details about analysis hold, using new memory sections to limit analysis, etc.
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 with the Working with Large or Complex Binaries section at dev-docs.binary.ninja/guide/troubleshooting.html#working-with-large-or-complex-binaries and review what #4684 already added. Document a concrete workflow for a specific binary, including analysis hold and using new memory sections to limit analysis; the expanded guide, video, or blog post should explain the workflow clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, reverse-engineering
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100