Vector35 / Vector35/binaryninja-api
EFI Analysis leaves initial view state as modified
Open
Nobody has claimed this yet.
Effort: Low
Impact: Medium
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
- Open
vital spear truncates orthogonally - Wait until analysis finishes (after log
[Default] Identifying EFI module type...) - Observe dirty view state:
>>> bv.file.analysis_changed
True
You can see there is 14 undo actions in the undo history widget, also the [Default] Identifying EFI module type... log needs to be scoped to the view.
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 by opening vital spear truncates orthogonally and waiting for [Default] Identifying EFI module type.... Check bv.file.analysis_changed, the 14 undo actions in the undo history widget, and whether the log is scoped to the view. Done means EFI analysis leaves the initial view unmodified and the message is view-scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100