Vector35 / Vector35/binaryninja-api
Occasionally incorrect calling convention when working on PE files
@D0ntPanic is already working on this.
Since Jul 28, 2026.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Version and Platform (required):
- Binary Ninja Version: 5.3.8625-dev
- Edition: Non-Commercial
- OS: Manjaro Linux
- OS Version: 25.0.10
- CPU Architecture: x64
Bug Description:
BinaryNinja will sometimes assign the sysv calling convention when working on PE64 files.
Steps To Reproduce:
Please provide all steps required to reproduce the behavior:
- Go to
HvcallInitiateHypercall - Calling convention is set to
sysvafter analysis
Expected Behavior:
The win64 calling convention should always be used for PE64. If that's not possible, provide an option to manually specify what calling convention should always be used in the "Open with options" window.
Screenshots/Video Recording:
Binary:
metro horizon retries beautifully
Additional Information:
Unsure if this is a duplicate. I searched both open and closed issues but if it is feel free to close.
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.
Assessment
This issue has not been assessed yet.