M
Malcolm Davey
We have found a the change in behaviour of the SetUnhandledExceptionFilter API call.On windows server 2016, this enables any uncaught C++ exceptions to be handled by a registered filter, including on our worker threads.In our filter callback we have alternative handling, including stopping the applications from terminating,but on windows server 2022, our filter doesn't get called for C++ exceptions on our worker threads, but the application is terminated instead.There is no mention of a change in behaviour of this on certain windows versions in the windows API documentationSome investigation h
Continue reading...
Continue reading...