Should an ASSERT_VALID stop in the debugger ?

Question

4.00/5 (3 votes)

See more:

VS2008

, +

Should an ASSERT_VALID stop in the debugger ?

I'm trying to trace a crash when our application closes.

It crashes somewhere in CFrameWnd::OnClose (in a ::DestroyWindow).

In the message log there is a ASSERT_VALID that is logged; but the debugger does NOT stop on the assert:

C++

ASSERT_VALID fails with NULL pointer.

Not much help that gives me; no code reference (file or line number or allocation number)

I tried enabling all the exceptions, but no change.

Am I missing something ?

Thanks.

Posted 1-Aug-12 3:43am

Maximilien

Updated 1-Aug-12 5:24am

v2

Add a Solution

Comments

nv3 1-Aug-12 11:20am

Did you mean "... but the debugger didn't stop on the assert"?

Maximilien 1-Aug-12 11:24am

oh !!!! yes! ( I will edit the original posts!!) thanks for that.

Maximilien 2-Aug-12 7:16am

@armagedescu.

I does not break in the debugger, so no call stack.
The report in the meesage area does not show context (line/file/function/method), so I cannot easily find out why it crashes,
anyway, the question was more about the ASSERT_VALID not breaking than debugging.
Thanks.

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)

nv3 · Answer 1 · 2012-08-01T04:01:00

This type of crash typically occurs when a frame window or view is being deleted via two separate code paths. For one, these windows normally have a

delete this;

in their OnNcDestroy function and de-allocate their object automatically. If it is also accidentally deleted by the user, the mentioned problem occurs.

Perhaps that gives you some help with tracing that one down.

Albert Holguin · Answer 2 · 2012-08-01T04:27:00

Solution 2

Quote:
Should an ASSERT_VALID stop in the debugger ?

Short answer, yes.

It won't tell you directly what led to the assertion, but you should be able to look at the call stack and trace back to see what part of your code led to the assertion being triggered.

Posted 1-Aug-12 4:27am

Albert Holguin

Comments

Maximilien 1-Aug-12 10:49am

Well the ASSERT_VALID does not stop the debugger, that is why I'm asking the question.

Albert Holguin 1-Aug-12 11:38am

Oh, I see... I misunderstood... it should stop the debugger. I guess now I see how that's a head scratcher.

Albert Holguin 1-Aug-12 11:41am

Wonder if perhaps you've either overriden the macro or perhaps defined the AssertValid() method in a manner that prevents the usual pop-up.

Maximilien 1-Aug-12 11:44am

Yes, will have to look into that.

Thanks,

Will report back when I find something useful.