Re: Handling Crashes in C++ program internally

From:

"SvenC" <SvenC@nospam.nospam>

Newsgroups:

microsoft.public.vc.language

Date:

Wed, 1 Apr 2009 14:07:17 +0200

Message-ID:

<OmT6nJssJHA.5912@TK2MSFTNGP02.phx.gbl>

Hi Sachin,

1. i think i would need try catch for following reason ..

// Somthing bad happens in function2 and Win32 exception is raised
// Say NULL pointer is tried to deferenced
void func2()
{

....

       try
      {
           char* ch = NULL;
            strcpy(ch, "msdn");

That is a bug! Fix the bug and you will not get an exception.
Do not misuse exceptions as mechanism to handle bugs!

in Above Example whenever Exception occur my_handler will be called
and it will simple throw a translated exception which my program can
understand .( I have a custom exception class SE_Exception )
so using try catch help to free resources or memory which otherwise
could
have caused undefined behavior or memory leak.

Use RAII for this: Use classes to hold the resources so that they are freed
in
the destructor when objects of those helper classes get out of scope. Search
for RAII and smart pointers.

2. I agree with Writing Dump files which would help to locate the exact
issue, but in release version its unacceptable to see any crash windows
or
any type of error window which will stop the tool which runs automation
environment . if this tool stops it will stop further tools in chain. So
i
am trying to just record , and move those exception files and go ahead ..

When any tool in the chain has a bug the tools running afterwards may
work with incorrect data. I consider this dangerous:

try
{
airplane->closeDoor();
}
catch(...)
{ }

airplane->takeOff();

Now looking at the nested function calls i have adding try catch is
mandatory at all level so that i can free memory and resources in
respective
function.

Do you still think there is better alternative?

RAII and smart pointers.

--
SvenC