Vector35 / Vector35/binaryninja-api
Add settings for auto-create unbound (unbacked) memory regions
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
What is the feature you'd like to have?
For those memory regions that is not backed by file, BN won't create related structures/objects, so we must create it by hand, however it would be nice to got setting (checkbox) to set so it would be done automatically.
Additional Information:
For example in macho __DATA is a dynamic segment, so it may be not presented in the file fully, but get the virtual size bigger than physical, however the binary may use such memory, so BN even render it, but won't create the region, so for example BinaryView won't let to patch such memory.
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
The issue names no files, tests, or entry points. Start by locating the settings implementation and the code that creates memory regions for unbacked Mach-O segments. Define the setting's scope and verify that enabling it creates patchable regions while preserving existing behavior when disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100