Vector35 / Vector35/binaryninja-api
Expand memory representation to encompass a wider diversity of situations
Open
Nobody has claimed this yet.
Component: Core
Effort: High
Impact: High
UI: Memory Map
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
The current memory model needs to be expanded to support many different situations. This is the umbrella issue to cover a set of problems whose root cause is both our memory representation an how it can be manipulated through the API/UI.
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
This is an umbrella issue and names no files, tests, or entry points. Start by identifying the concrete memory-representation and API/UI problems covered by this issue; a separately scoped child issue with an explicit expected result is needed before completion can be defined.
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
- 20/100