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 Jun 16, 2019. It is now read-only.
The current approach to analyzing the stack frame in RemillStackRecovery can be supplemented by analyzing the location of the return address of the caller relative to the top of the stack stored in the stack pointer. A thing to note is that this needs the ABI to define that the callee is responsible for cleaning up stack.
This kind of analysis could provide information about the number of stack parameters passed into the callee without the callee actually accessing any of the parameters. Which is useful when analyzing callsites of the callee so that we won't recover too many or few parameters.
The text was updated successfully, but these errors were encountered:
The current approach to analyzing the stack frame in
RemillStackRecovery
can be supplemented by analyzing the location of the return address of the caller relative to the top of the stack stored in the stack pointer. A thing to note is that this needs the ABI to define that the callee is responsible for cleaning up stack.This kind of analysis could provide information about the number of stack parameters passed into the callee without the callee actually accessing any of the parameters. Which is useful when analyzing callsites of the callee so that we won't recover too many or few parameters.
The text was updated successfully, but these errors were encountered: