Re: Exception Handling

From:

"William DePalo [MVP VC++]" <willd.no.spam@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Tue, 17 Oct 2006 20:49:00 -0400

Message-ID:

<#viD18k8GHA.5020@TK2MSFTNGP03.phx.gbl>

"Ben Menashe" <BenMenashe@discussions.microsoft.com> wrote in message
news:6A35789E-9326-4A82-8B48-EFD8F1A8491C@microsoft.com...

Thanks so much for this info Will.

You are welcome.

I was able to catch the exception now by
just switching to the asynchronous mode.

OK.

So by converting it to a C++ exception what am i gaining ?

Standard behavior.

There may be a performance implication as well, but I'm not sure about that.
/EHa tells the compiler that exceptions can come out of nowhere and so it
has to keep all that stack unwinding machinery in place so it can destruct
automatic objects when an exception occurs.

All I really want to do is report the error and restart the service if it
happens...

In that case, I wonder if you just ought to take the default behavior and
configure the service control manager to restart the service.

I guess I'll have to keep that exception code as simple as
possible so it has no way of causing another exception.

That's wise.

That way we can track that there are still problems out there,
but our users will be unaffected and will not know that a service
just crashed on their machines.

My little exception class tries to report on the error and its location.
Perhaps you can do something similar until you resolve the issue.

Regards,
Will