Re: Handling Unknown Exception within a Dialog App
After the execption is thrown, can you trace the call stack back to
somewhere in your own code? That would tell you where you would need the try
catch statment to handle that execption.
AliR.
"BartMan" <MaskProg@community.nospam> wrote in message
news:104E73B0-8307-4DA3-BF5D-B597F5693B10@microsoft.com...
Greetings,
I recently began maintenance work on a Legacy application which was done
in
Visual C++ 6.0, on a windows xp machine.
It uses several 3rd party activex and atl com components, and seems to
work
in pretty stable manner. However sometimes when the application exits it
has
an exception sometimes occurs, and causes the exit to throw up an
exception
error.
So is there a way to trap every exception which is thrown similar to what
is
done in .net? So I can trap an exception, and then allow the application
to
exit gracefully?
This is the code that I have tried using (it worked for handling some
apparent NULL pointers problem which exist in one of the 3rd party
ActiveX
controls). It caught some of the exceptions, but not all. Is there
anything
else I can do?
// Code I used to catch some of the exceptions.
(ie:)
static void my_translator(unsigned code, EXCEPTION_POINTERS *)
{
throw code;
}
BOOL CMyTestApp::InitInstance()
{
_set_se_translator(my_translator);
// Handle translated errors
TRY
{
// Handle c++ errors
try
{
AfxEnableControlContainer();
CMyTestDlg dlg;
dlg.DoModal()
}
catch(...)
{
}
CATCH_ALL(e)
{
// Handle Error
}
END_CATCH_ALL
return FALSE;
}
So any suggestions on catching any com or ActiveX errors which are
generated
in the application?
Thanks in advance for any suggestions!