I’m using MiniDumpWriteDump with MiniDumpNormal parameter to dump call stack in SEH exception handler. When I open the dump in VS, I can’t see the callstack. I did see it with the same code two days ago when I started experimenting with dumping. I’ve changed something, and I don’t understand what. This is a debug build (and I even saw call stack from a release build all right). I can see call stack fine in the debugger, if I put the breakpoint at MiniDumpWriteDump call. I can see call stack after opening the dump in VS, if the dump wasn’t written from within the exception handler.
What can be the cause of stack not showing up?
That’s what my dump-writing code looks like
P. S. I compile with /EHa. Also tried disabling C++ exceptions at all (that definitely worked two days ago). And, of course, .pdb files are generated fine.
P. P. S. And this is what I mean by saying “call stack is not showing up”.
In some circumstances, the debugger is not able to reconstruct the whole stack.
In this case, you need to open the dump with WinDbg and reconstruct the stack manually.