Re: Filtering 'Access Violation' error inside a try-catch block

From:

"Alexander Grigoriev" <alegr@earthlink.net>

Newsgroups:

microsoft.public.vc.language

Date:

Mon, 12 Oct 2009 22:07:47 -0700

Message-ID:

<eonfcM8SKHA.1268@TK2MSFTNGP04.phx.gbl>

Make a separate DLL hosting process, and design a communication scheme
between it and your main app. If the dll host crashes, your main process is
still alive.

"Sanje?v" <swtbase@gmail.com> wrote in message
news:f1a5991f-3e7e-49cb-9481-938a7384e5b2@m7g2000prd.googlegroups.com...

Though why I would wanna catch an access violation, isn't related to
the problem. Here's why, anyway:

My program allows third-party dlls to be loaded into its address space
as plugins. But I surely wouldn't want my application to crash due to
a faulty third-party dll doing something stupid like dereferencing a
NULL pointer. So, I thought why not guard the point where my
application calls functions in the third-party dll and if an access
violation is thrown, just unload the faulty dll and notify the user
that a problem has occurred due to a plugin and the program has
downgraded? I only want to catch an access violation error and allow
my application to crash (default behaviour) if other serious errors
occur.

A 'try/catch(...)' willl catch an access violation error but is not
able to identify if its really an access violation or any other error.
Is __try/__except only the way out of this?

-Sanjeev