Vector35 / Vector35/binaryninja-api
exception handler analysis
Open
Nobody has claimed this yet.
Component: Core
Effort: High
Impact: Medium
Scenario: Malware
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
From @psifertex on August 10, 2015 7:23
we should do it.
Copied from original issue: Vector35/binaryninja#43
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
The issue names no files, tests, entry points, or concrete acceptance criteria. Start by reviewing the original Vector35/binaryninja#43 issue, then establish the intended scope and what successful exception-handler analysis should produce before identifying implementation and test locations.
Written by the indexing model from the issue text.
Assessment
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100