Getting control of Assertion in VC++

Question

0.00/5 (No votes)

See more:

I am preparing one utility for testing some of the application. I need some help in some part of it.
Suppose I have launched one debug build application. Then in between one assertion has come which was put by developer. So I have to do 2 tasks:
1) Get the content of that assertion
2) Click ignore or some how ignore the assertion.
After this initial application will resume.
I am not having the code with me. So modifying existing exe is out of question.

Posted 2-Feb-10 0:41am

Member 1544087

Updated 2-Feb-10 2:51am

Add a Solution

2 solutions

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)

Avi Berger · Answer 1 · 2010-02-02T06:00:00

Member 1544087 wrote:
testing some of ... the application ...
I am not having the code with me. So modifying existing exe is out of question.

I am inferring from this that you are acting as a tester identifying bugs for a developer to fix.

An assertion often indicates a serious error encountered in a program. Attempting to continue past one is likely to exhibit bad behavior from the program caused by the problem already identified, so is of doubtful usefulness. You will then be noting further program misbehavior from the same source you have already flagged. I would suggest instead that after documenting this for the developer (what you did to trigger the assert, what needs to be done to repeat it, and a screen shot of the message pasted into the document you are creating) that you start a new test run exercising other paths through the program. Come back and proceed past where the assertion was after the developer has provided a fix and you won't be banging you head against peculiar symptoms from the bug you have already turned up and characterized.

Christian Graus · Answer 2 · 2010-02-02T00:44:00

Solution 1

Your best bet IMO is to replace the ASSERT macro so that it works the way you want it to.

Posted 2-Feb-10 0:44am

Christian Graus