ExcHndl doesn't work on Windows 10 about drmingw HOT 4 CLOSED

I just ran the sample and tests on Windows 10 and they seem to work fine -- SetUnhandledExceptionFilter gets called.

Try building and running the sample that comes with DrMingw. See whether a sample.RPT gets called or not.

One limitation of ExcHndl is that it only sets the unhandled exception filter on one thread. Perhaps your app is multi-threaded and the exception is happening on a different thread?

from drmingw.

Also note that exceptions inside WindowProc never get caught. See the remarks at the bottom of https://msdn.microsoft.com/en-us/library/windows/desktop/ms633573.aspx

from drmingw.

Thanks. I'll try check example later
Yes, my app is multi-threaded. But on Windows 7 crash reporting works fine. Also I use hack like this. Maybe technique described there not applicable on Windows 10

from drmingw.

Yes, I know first hand how trying to intercept Windows APIs is a tricky business. You can see in https://github.com/apitrace/apitrace/tree/master/inject all sort of tricks I had to do in another project of mine.

Another (and probably more portable) approach would be for your application to have a __try { .. } __except {...} as early as a possible (preferably in the main), and then call ExcHndl somehow. But again, this will only be practical for single thread apps.

If you're still convinced there's a bug in ExcHndl and can provide a small test case showing the issue, please reopen this issue I'll try to look into. Until then I'll presume the the issue is elsewhere.

from drmingw.