-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown calling convention for ARM v9 binaries? #66
Comments
Thank you for letting us know! |
@ITAYC0HEN Can you point me how can I add support for this binaries? |
I was looking for the place in the code (https://github.com/radareorg/r2ghidra-dec/blob/master/src/R2Architecture.cpp#L26) to show you how to fix it, but then accidentally fixed it myself 🙈 r2's arm32 cc maps to __stdcall in sleigh so I added that. It can still happen that you see incorrect function args, especially for imported functions, but that is better tracked in #73. |
Nice! So how can I introduce this to my Cutter (Currently stable release)? Should I build from source or do you have some sort of nightly builds stream? |
The best way is to build all from source, but a new release is scheduled soon too. There are no nightlies provided unfortunately. |
Unless you're on windows and then you can download the artifact from AppVeyor |
Environment information
Describe the bug
I'm trying to analyze ARMv9 binary, compilled with
arm-linux-gnueabihf-gcc
and getting the following warnings in decompiler:I've tried different types of analysis and different types of architecture settings. The best result is achieved with automatic
aaa
presethow can I provide Cutter with calling convention type or add support for ARM v9?
Screenshots
The text was updated successfully, but these errors were encountered: