Improve docs on viewing memory
Open
Nobody has claimed this yet.
documentation
Impact: Low
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
We need to better explain this to the users: https://docs.binary.ninja/guide/debugger/index.html#viewedit-memory
Also https://github.com/Vector35/debugger/issues/520 is probably the way to go
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 linked View/Edit Memory section in the Binary Ninja debugger documentation and review the related issue Vector35/debugger#520. Clarify the user-facing explanation there, with the documentation section updated so users can understand how to view memory.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100