Best way to handle Assertions failures in MFC applications.

Question

0.00/5 (No votes)

See more:

Hello Friends,

i have created the application with type dialouge based and integrated the the FranmewinEx as Base class window.when i docuked two Docuable pane classes sentimentally its working fine in release mode.means opening the openGL Enabled contexts are visible and rending the fine..when i run the same code in deburg .its giveing some dubug assertions failures while window creation.
its crash window Thread after that dubug break function.i would like to know the procedure of handle this type of exceptions. and i would like to know will it be resolved with latest MFC releases,
and i have used MFC 10.0 Visual studio 2010 Please provide the guidance for later updates can i use the code 2010 to 2013 visual studio if so please let me know the way of conversion..

thanks and regards
srinivas.

Posted 9-Sep-13 1:49am

SrinivasLadi

Updated 9-Sep-13 1:57am

v2

Add a Solution

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 · 2013-09-09T03:16:00

Best way (and actually, the only way) to handle assertion failures is to go back to source code and fix the bug.

The assertions are not designed to be handled as other exceptions, which may or may not be acceptable. The purpose of the assertion is to capture the situation when you, as a developer, think that some predicate is always true, so your check it up, but it turns out to be false during runtime. It simply means that you made a bug. An assertion is a development tool, like debugger, tracing and similar things, not a runtime facility.

Please see:
http://en.wikipedia.org/wiki/Assertion_%28computing%29[^].

—SA