How do I get information about an exception?

Question

0.00/5 (No votes)

See more:

I'm using the following syntax to catch exceptions using Visual C++ 1.0:

TRY
{
   //Some code
} 
CATCH(CException, e)
{                                   
  //Get info about error here?  Members of variable e?		
}
END_CATCH

I'd like to get more information about the exception when it is caught. Can I do that? If so, then how, please?

Regards,
Mike

Posted 6-Mar-14 12:03pm

mla154

Add a Solution

Comments

Aravindba 6-Mar-14 22:39pm

hi u need to what error in catch block ? just use e ,form e u can get what error in ur codings

mla154 7-Mar-14 7:55am

Can you explain this further? How do I use 'e' to get the error?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2014-03-06T14:06:00

You have as much information as the object c can carry, no more, not less.

The resolution is on the throwing side. You may need to throw you own objects of your own exception types, so make sure they are informative enough. Often, such custom exceptions add just information on the environment. For example, you catch the exception related to integer division by zero. You can catch this exception and re-throw it, but not of the same type. You can have your own exception type designed to explain the circumstances, why that division happened, in what semantic operation, and throw that exception, instead of original "low-level" exception. This is one of the purposes of structural exception handling. Another, most important one is isolation of "regular" code from exceptional. Practically, you should not handle exception too locally.

—SA