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
Bug Description:
Binary Ninja believes that control flow can return from __Unwind_Resume, which is not the case. This results in Binary Ninja thinking execution continues to the line after __Unwind_Resume, which can sometimes be the start of a function. This creates confusing and bloated decompilation output.
Expected Behavior: __Unwind_Resume should be marked __noreturn so that it doesn't fall through to whatever code comes after the call.
Additional Information:
This issue occurs when working with Mach-O binaries, I'm unsure if it extends to other binary types because I assume the type information is coming from a Mach-O specific type library.
The text was updated successfully, but these errors were encountered:
Version and Platform (required):
Bug Description:
Binary Ninja believes that control flow can return from
__Unwind_Resume
, which is not the case. This results in Binary Ninja thinking execution continues to the line after__Unwind_Resume
, which can sometimes be the start of a function. This creates confusing and bloated decompilation output.Expected Behavior:
__Unwind_Resume
should be marked__noreturn
so that it doesn't fall through to whatever code comes after the call.Additional Information:
This issue occurs when working with Mach-O binaries, I'm unsure if it extends to other binary types because I assume the type information is coming from a Mach-O specific type library.
The text was updated successfully, but these errors were encountered: