Vector35 / Vector35/binaryninja-api
"segments" section in memory map fonts are not monospace
Open
Nobody has claimed this yet.
Component: UI
Effort: Low
Impact: Low
UI: Memory Map
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Much earlier in dev there was a regression for fonts in the memory map to be non-monospace and unfortunately the fix at the time didn't actually fix segments, just sections. Need to identify the root cause and fix it.
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 by reproducing the memory map font behavior and compare the "segments" section with the already-fixed sections. Trace where each section's font is assigned and identify the root cause; done means segments render in a monospace font without regressing sections.
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