Python memory map API is kinda awkward
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- api, reverse-engineering
Research direction
Start with the Python MemoryMap API entry point and review how regions, iteration, and flags are currently exposed. Done means the API provides an object or equivalent access for regions, supports iterating all regions, and accepts the flag representation needed to copy flags between regions.
Written by the indexing model from the issue text.
Description
Version and Platform (required):
- Binary Ninja Version: 5.2.8236-dev Ultimate, d8af0ff0
- OS: macos
- OS Version: 26.0
- CPU Architecture: arm64
Bug Description:
I used the MemoryMap API for the first time today and found it a bit awkward to use. I was writing a small script to extract the flags for each memory region into a dictionary so they could be used to copy the same flags to an existing database (to help recover from #7354).
I ended up with:
import functools
{ bv.memory_map.get_active_memory_region_at(s.start):
functools.reduce(lambda a, b: a | b, bv.memory_map.get_memory_region_flags(bv.memory_map.get_active_memory_region_at(s.start)), 0)
for s in bv.segments
}
I had expected it to look more like:
{ region.name: region.flags for region in bv.memory_map }
Specifically:
-
There's no object to represent a memory region.
Looking up a region by address gives you back a name. To query properties of that region you pass the name to functions on
MemoryMap. -
There's no way to iterate all memory regions.
MemoryMapimplements__len__, but not__getitem__or__iter__. -
get_memory_region_flagsreturns asetcontaining zero or moreSegmentFlag, butset_memory_region_flagsaccepts aSegmentFlag.In order to take the flags from one memory region and apply them to another, you have to do something like
reduce(lambda a, b: a | b, flags, 0)to convert from the set toSegmentFlag.set_memory_region_flagsshould probably accept both a set orSegmentFlag.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
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.
More from Vector35/binaryninja-api
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Vector35/binaryninja-api#8540 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Vector35/binaryninja-api#8516 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Vector35/binaryninja-api#8503 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8446 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8444 ·
All issues in Vector35/binaryninja-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·