|
seems you are right deroko
i thought the cpu overwrites the stack in the same second the exception occurs
but the stack is overwritten later
do you know how exceptions are dispatched when a debugger is around?
till now i thought everything starts at KiUserExceptionDispatcher, but it seems its not the very first one that is informed by windows when a debugger was used
maybe the best solution is to write a small driver that hooks int1 and handles the exception stack-safe
hmmmhm
|