I'm trying to create my own app crash handler that collects the minidump files following this somewhat outdated sample. It uses the MiniDumpWriteDump() API but after reviewing the latest MSDN page for it I came across this statement in the Remarks section:
Quote Originally Posted by MSDN
MiniDumpWriteDump should be called from a separate process if at all possible, rather than from within the target process being dumped. This is especially true when the target process is already not stable. For example, if it just crashed. A loader deadlock is one of many potential side effects of calling MiniDumpWriteDump from within the target process.
So my question is, if I can't call MiniDumpWriteDump from the same process that crashed, how is it suggested to be called? I mean it won't have access to the stack context if I call it from another process....