MS Antispyware interferes with exception handling

[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

 

[Andre Da Costa]

My goodness Eric, did you hack the program? A lot of what you said I don't
understand, but it sounds like a possible bug between Service Pack 1 and
MSAS.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

 

[Guest]

Hack the program? Definately not.

I created a standalone test program that instruments the
exception handlers as per MS instructions, then tests the
handlers by causing exceptions to occur.

The upshot is that programs that want to or need to handle
the "unhandled" exception (the last ditch handler) will
fail and you will get no information about why your program
crashed.

Regards,
Eric

 

[Andre Da Costa]

You need to participate in these groups. ;-)
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm