Vector35 / Vector35/binaryninja-api
Adding a memory region silently truncates when synthetic builtin section is hit
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Reported by @VisualEhrmanntraut on the public slack:
adding any memory region (before the builtins?) with “Add Memory Region” results in its length always being 0x30 and no flags (edited)
https://github.com/user-attachments/assets/1678e111-ec26-42cf-ac59-ffbf93e9e5bf
Can confirm that the action silently fails inside the core when adding the memory region. Oddly enough it is fine if you create the memory region inside of the section and then continue past.
https://github.com/user-attachments/assets/b81cd945-a053-4935-a054-c040e67756bc
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
Reproduce the issue with the “Add Memory Region” action, particularly when adding a region before or at the synthetic builtin section, and inspect the core path where the action silently fails. The fix is complete when a newly added region retains its requested length and flags in that position, while the existing behavior inside the section and after it remains correct.
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
- Needs clarification
- Newbie friendliness
- 35/100