Vector35 / Vector35/binaryninja-api
Better Support For Memory Allocation Routines
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Currently, BN understands certain allocation routine (e.g., malloc, VirtualAlloc) and can deal with its return value properly when the user creates s (https://docs.binary.ninja/guide/type.html#smart-structures-workflow). However, this is currently done purely from the UI. The notion of an allocation routine and the BN's handling is also very little known. We should probably:
- Mention what is an allocation routine and how BN handles it in the docs
- Move the code dealing with allocation routine into the core
- Allow the user to mark a function as an allocation routine, alogn with the size of the allocation
- Add support for more allocation routines, e.g., mmap
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 smart structures workflow documentation and the existing UI handling for allocation routines. Done means documenting the concept, moving the handling into the core, allowing users to mark functions with an allocation size, and adding support for routines such as mmap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100