You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All failed methods have a control flow where __stack_chk_fail will be called after error(1,..) in the cfg.
This control flow is not correct, because with specific optimization levels (min binary; -O1, -Os), the compiler knows/accounts for that error(1,...) will not return.
Therefore __stack_chk_fail will not be called even if there is no assembly instruction between them.
What happened?
The decompiler crashes with a RuntimeError in remove_stack_canary during preprocessing.
How to reproduce?
Decompile size_opt in uniq or main in one of the other samples given below.
remove_stack_canary_runtime_error.zip
Affected Binary Ninja Version(s)
3.2.3814
The text was updated successfully, but these errors were encountered: