Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it possible in some way to access local variables (and method arguments) during stack unwinding after an exception is thrown? It is quite trivial to get methods names using StackWalk64 but I wonder if I can get to variables so I can better understand the problem.
Even if you run the process under a debugger (including your own home-made debugger), it is not possible to get local variables AFTER exception is thrown and you reach the exception handler. The call stack is already unwinded.
You may however get the call stack (not in all circumstances), using SEH instead of C++ exception handling.