Vector35 / Vector35/binaryninja-api
Undefined type presists in anaylsis
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Version and Platform (required):
- Binary Ninja Version: 4.2.6541-dev
- OS: Mac
- CPU Architecture: M2
Bug Description:
After undefining a type, it persists in the IL (even across reanalysis).
Steps To Reproduce:
- Open any binary
- Define a user type struct
- Set that type on a variable (struct* or struct)
- Undefine the struct
Expected Behavior:
The type of the variable should be reset to whatever the auto type from analysis was.
Screenshots/Video Recording:
https://github.com/user-attachments/assets/f1e09a0d-76cf-4cb1-90c4-07497899719b
Josh tested this in 4.1 and 4.0 and was able to repro it.
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
Reproduce the issue in Binary Ninja 4.2.6541-dev on macOS with an M2 by following the four listed steps, then inspect the type-handling and reanalysis entry points implicated by the IL state. Compare the variable's type before and after undefining the user-defined struct and across reanalysis. Done means the variable returns to its automatically inferred analysis type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100