Vector35 / Vector35/binaryninja-api
confusing behavior in mlil expr_type
Open
Nobody has claimed this yet.
Component: Core
Core: MLIL
Effort: Medium
Impact: High
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Describe the bug
expr_type of MLIL_VAR differs from its src.type
To Reproduce
Steps to reproduce the behavior:
- test_case.zip
- Open test_case binary
- Execute test_case.py content in console
- It prints "void*" and "Test"
Expected behavior
It should print equal types "Test"
Additional context
Binary Ninja Version: 2.3.2763-dev Personal, 426a99ac
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 attached test_case.zip and the test_case.py steps, reproduce the differing "void*" and "Test" output in Binary Ninja, and inspect MLIL_VAR expr_type alongside its src.type. Done means the reproduced case reports equal types as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100