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
Only the top frame can be potentially in an epilog; further frames should point to a function call, which is by definition outside an epilog. Instruction parsing can be skipped in such cases as a small optimization.
An exception is interruption coming from signal-like primitives. There are no signals on Win32, but access violation exceptions work similarly. These will push a KiUserExceptionDispatcher entry on stack along with a MACHFRAME entry. We should make sure to treat anything beyond a MACHFRAME entry as the same as a first frame.
The text was updated successfully, but these errors were encountered:
Actually, this was more critical than I thought since the lookup address is shifted by 1 for return address frames. Which means that instruction analysis was basically reading garbage all the time.
Only the top frame can be potentially in an epilog; further frames should point to a function call, which is by definition outside an epilog. Instruction parsing can be skipped in such cases as a small optimization.
An exception is interruption coming from signal-like primitives. There are no signals on Win32, but access violation exceptions work similarly. These will push a
KiUserExceptionDispatcher
entry on stack along with a MACHFRAME entry. We should make sure to treat anything beyond a MACHFRAME entry as the same as a first frame.The text was updated successfully, but these errors were encountered: