Vector35 / Vector35/binaryninja-api
Workflow for lifter checking
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Make a PluginLifterDebugWorkflow with extra lifting debug messages (tags??) that may be too slow to run on normal workflows. Would be a great resource for lifter plugin devs
Many good checks in Liftcheck: https://gitlab.com/rsnyder/binja-riscv/-/blob/master/src/liftcheck.rs
Could throw in other checks too if there are good ideas
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 reviewing the proposed PluginLifterDebugWorkflow and the referenced Liftcheck implementation at src/liftcheck.rs. Determine which lifting checks and debug messages belong in the workflow, including whether tagged output is appropriate. Done means lifter plugin developers have a usable workflow with the agreed checks and diagnostics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, rust
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100