Vector35 / Vector35/binaryninja-api
stack slot re-use with different sized variables
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
We support splitting variables, but we don't currently have solid support for handling situations where a stack struct has part of it re-used later. This in particular will impact large golang functions with structures.
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 locating the variable-splitting and stack-struct handling code responsible for reusing part of a stack variable with a different-sized variable. Reproduce the behavior with a large Go function containing structures, then verify that stack slot reuse is represented correctly without breaking existing variable splitting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, go
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100