Vector35 / Vector35/binaryninja-api
Show function argument variables at call site
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Within a function, incoming arguments are named as arg_1, arg_2...; however, in the caller, the argument variables to the callee are not documented. It would be nice if, beside a call instruction, something like this showed up: call sub_0xf00 {var_x, var_y, var_z} meaning that the local variable var_x in the current function is passed as the first argument to sub_0xf00.
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 public API's representation of call instructions and how incoming arguments are currently exposed as arg_1, arg_2, and later. Trace how local variables are associated with arguments at a call site, then verify that the displayed variables match the callee's argument order and the requested call-site format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100