Consider using SetProcessUserModeExceptionPolicy in future versions of CrashRpt

[Farshid Lashkari]

Hi,

I'm in the process of integrating CrashRpt into our MFC based software. It is an amazing library and very easy to use, kudos!

However, I just spent the past few days figuring out why some crashes were not triggering the crash report dialog. Also, when the dialog was triggered, the stack trace of the crash dump was bogus. I finally came across this page (http://code.google.com/p/crashrpt/issues/detail?id=104) where a user mentions that this is a problem for win32 applications on x64 systems. The workaround posted by the user completely solved my problems. I just added a call to SetProcessUserModeExceptionPolicy disabling PROCESS_CALLBACK_FILTER_ENABLED, and now the crash reporting works properly and the stack traces look correct.

I think it might be a good idea to add this to future versions of CrashRpt, either automatically disable process callback filter or add it as an option. It might also be a good idea to update the FAQ with that information as well.

Cheers,

Farshid

[zexspectrum]

Hi, 

Thanks for this information. I added it to the issue  http://code.google.com/p/crashrpt/issues/detail?id=104 

I'm planning to fix this for the next release.