E
Eric Fredericksen
FYI
The UnhandledException exception handler mechanism no
longer works correctly if MS Antispyware is installed on
Windows 2003 Server with SP1.
I have not tested this on other OS versions SP combinations.
The handler appears to be installed correctly immediately
after the installation call to SetUnhandledExceptionFilter.
However, when a test exception is generated (throw an
uncaught C++ exception) the C++ runtime popus up its modal
dialog and the installed handler is never called.
Uninstall MS Antispyware and the mechanism works correctly.
Reinstall, and it fails again.
This bug occurs when the GUI is running or not, and also
when 'real time protection' is NOT enabled. That would
imply that something 'real time' is occurring without my
permission.
Regards,
Eric
The UnhandledException exception handler mechanism no
longer works correctly if MS Antispyware is installed on
Windows 2003 Server with SP1.
I have not tested this on other OS versions SP combinations.
The handler appears to be installed correctly immediately
after the installation call to SetUnhandledExceptionFilter.
However, when a test exception is generated (throw an
uncaught C++ exception) the C++ runtime popus up its modal
dialog and the installed handler is never called.
Uninstall MS Antispyware and the mechanism works correctly.
Reinstall, and it fails again.
This bug occurs when the GUI is running or not, and also
when 'real time protection' is NOT enabled. That would
imply that something 'real time' is occurring without my
permission.
Regards,
Eric