analyzing the crash dump with __except

Question

Suppose I have the following code

main()
{

   __try 
  {

   //---> SEH EXCEPTION HAS HAPPENED HERE

  }
   __finally
  {

   //---> CRASH DUMP WAS TAKEN HERE

  }

}

The crash dump was taken at the "--->" marked place. Can I know from userdump what was the original exception that brought us there. I cannot find any info in stack trace (seems just like normal execution without exception handler)

UPD: Sorry guys seems like the exception wasn't in the this thread, otherwise finally handler would be clearly called from __except_handler during the unwind phase. Need to close

It cannot be normal if there's an exception. What are the faulting instruction and the exception code? Most likely it's a bad pointer/array index or memory corruption that caused it. — Alexey Frunze, Apr 25 '12 at 09:30

score 1 · Answer 1 · answered Apr 25 '12 at 09:14

1

Use WinDbg and follow the details on this blog post: http://blogs.msdn.com/b/slavao/archive/2005/01/30/363428.aspx WinDbg can be downloaded from here: http://msdn.microsoft.com/en-us/windows/hardware/gg463009

answered Apr 25 '12 at 09:14

EdChum

376,765
198
813
562

score 1 · Answer 2 · answered Apr 25 '12 at 10:07

1

You are just doing it wrong. The crash dump should be made in the __except filter. Now .excr and !analyze will work just fine in the debugger.

answered Apr 25 '12 at 10:07

Hans Passant

922,412
146
1,693
2,536

analyzing the crash dump with __except

2 Answers2