Quote:
|
Originally Posted by MaRKuS-DJM
maybe it's worth to mention: a jump in the form of [XXXXXXXX*X*EAX] can't be found the way you described.
|
That is correct Markus, jump instructions do not leave a "trail" in the stack, so there is no simple way to backtrace them, only forward tracing will do, EXCEPT if you use a debugging tool whose link was posted by, I think Nikola. this debugger allows forward and backward LIVE tracing.
It apparently keeps a record track of the instruction path taking by the code, allowing you to backtrace to an arbitrary number of instructions.