Get the latest tech news
Disabling kernel functions in your process (2009)
Detecting and reporting unhandled exceptions with SetUnhandledExceptionFilter seemed logical, and, in fact, it worked... for a while. Eventually, we started to notice failures that should have been reported as a last-chance exception but weren't. After much investigation, we discovered that both Direct3D and Flash were installing their own unhandled exception filters! Worse, they were fighting over it, installing their handlers several times per second! In practice, this meant our last-chance crash reports were rarely generated, convincing us our crash metrics were better than they were. (Bad, bad libraries!)
Detecting and reporting unhandled exceptions with SetUnhandledExceptionFilter seemed logical, and, in fact, it worked... for a while. Thus, we chose to disable (with code modification) the SetUnhandledExceptionFilter function immediately after installing our own handler. After implementing this, it's worth stepping through the assembly in a debugger to verify that SetUnhandledExceptionFilter no longer has any effect.
Or read this on Hacker News
