Vector35 / Vector35/binaryninja-api
Ability to flag a function as 'opaque'
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Occasionally it's useful to suppress the application of information from a callee into the caller, for example recovered dataflow from a pure function or the exact set of clobbered registers.
Primary motivating use case is trivial functions that exist as targets to be patched at runtime, meaning any static analysis of their effects (or lack thereof) is not useful. Forcibly applying only the function signature and otherwise treating it as an indirect call covers this use case and gives people a way to prevent the 'inlining' of pure calls when that is undesirable.
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 public API and examples in this repository, then trace how function signatures, pure calls, clobbered registers, and indirect calls are represented. Done means callers can mark a function opaque so analysis applies only its signature and otherwise treats the call as indirect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100