Vector35 / Vector35/binaryninja-api
Provide an error message when write to the binary view fails
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
There are several reasons why an attempt to write to the binary view can fail, e.g., file is write protected, segment not backed by file, byte affected by relocation, etc. Right now, when any of these happens, it just fails silently. We should offer an error message to explain why it fails. Or at least, pop up a dialog to say the write failed.
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 locating the binary view write path and reproduce the listed failure cases: write protection, an unbacked segment, and relocation-affected bytes. Trace how each failure is currently handled; done means a failed write reports its reason or at least displays a write-failed dialog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100