I have asked a question about handling crashes of a command line tool in a C# application on stackoverflow. I was pointed to this forum for finding out, how to avoid that WerFault.exe jumps in and displays a crash report message for the command line tool, the crash of which I want to handle with my C# application.
Crashes are handled by Windows by default, visit Stack Overflow for a programmatic solution to hook into the process instead of waiting for a capture. But, you might not need to hook yourself:
Windows looks up
in order to know what debugger needs to be launched when a crass occurs.
The most usual generators are:
The most usual debuggers are:
Of these, you might be able to just let Dr. Watson or ProcDump do it's job,
after which you can open the debugging file for more information. These three links might get you going if you need to read the generated
Even better, you might be able to just use ProcDump and don't even need to set