Vector35 / Vector35/binaryninja-api
BNIL should handle address of structure member wherever the constant is in the expression
Open
Nobody has claimed this yet.
Component: Core
Core: HLIL
IL Optimization
Impact: Medium
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
BNIL coerces structure_pointer + constant + var to &struct_pointer->foo + bar but doesn't coerce structure_pointer + var +
constant to the same construct.
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 reproducing the two BNIL expressions shown in the issue and locate the coercion logic that recognizes a structure member address. Compare behavior when the constant appears before versus after the variable; done means both forms coerce to the same structure-member-plus-offset construct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100