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
{{ message }}
This repository has been archived by the owner on Aug 23, 2022. It is now read-only.
We could (and maybe should?) treat all two-byte interrupts (opcode CD xx versus CC) as noreturn? I know technically CD 03 is still an INT3, but no sane compiler would emit it, and we officially do not support obfuscated code.
For this specific case it obviously makes more sense to call the high level handler of RtlFailFast. Maybe we could have a Windows-specific CFG recovery fix here? Or, alternatively, a Windows-specific int 0x29 handler?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
mcsema-disass
does not recognize this call toRtlFailFast
as a no-return instruction, and so the following innocuous errors pop up:The text was updated successfully, but these errors were encountered: