Catching child process exceptions on windows?

Debug API is one option Here is a starting point in MSDN.

Debug API is one option. Here is a starting point in MSDN.

Thanks for the answer! I had thought of using some debugging API, but thought some applications which use some anti-debugging mechanisms to avoid cracking and/or revering could modify their behaviour if they detect they're being debugged by the fuzzer. I suppose if I can't find another option, then i'll have to use this debugging mechanism.

– fontanini Nov 30 '10 at 14:34 all the more reason to shoot people who try to reverse-engineer proof their code. – Chris Becke Nov 30 '10 at 14:44 It worked! Thanks a lot :D – fontanini Dec 1 '10 at 17:50.

Try to inject the following code into your child process: SetErrorMode(SEM_NOGPFAULTERRORBOX); Lookup the details of SetErrorMode in MSDN. Read about injection technique here: Injective Code inside Import Table.

Following on frast's answer, you can spawn the process as a child of a process with a suitable SetErrorMode. This (inheritable) setting determines which errors will result in dialogs popping out - I found your question while trying to achieve the exact same thing for an automated testing application. To avoid any error dialogs, use SetErrorMode( SEM_FAILCRITICALERRORS | SEM_NOALIGNMENTFAULTEXCEPT | SEM_NOGPFAULTERRORBOX | SEM_NOOPENFILEERRORBOX); Injection is probably overkill - better to use a wrapper process.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.