Runtime errors in Debug .exe

Question

0.00/5 (No votes)

See more:

In the Release mode, my program runs fine, no major problems!

I am getting some runtime errors which are only occuring in the "Debug" configuration. The program compiles fine in Debug mode.

I see a message box ->

Debug Assertion Failed!

Program: <program name="">
File: winocc.cpp
Line: 330

Sequentially debugging, led me to this in doctempl.cpp

// create new from resource
if (!pFrame->LoadFrame(m_nIDResource,
        WS_OVERLAPPEDWINDOW | FWS_ADDTOTITLE,   // default frame styles
        NULL, &context))
{
    TRACE(traceAppMsg, 0, "Warning: CDocTemplate couldn't create a frame.\n");
    // frame will be deleted in PostNcDestroy cleanup
    return NULL;
}

This is where the assertion pops up.

In the linker, these are my additional library dependies. Is something wrong here?

d3d9.lib strmiids.lib ole32.lib winmm.lib psapi.lib user32.lib

Any idea what I am doing wrong?
Thanks.

Posted 20-Apr-13 7:28am

weirdProgrammer-2

Updated 20-Apr-13 7:52am

v2

Add a Solution

Comments

Matthew Faithfull 20-Apr-13 16:33pm

Is your application multithreaded?

Sergey Alexandrovich Kryukov 20-Apr-13 22:15pm

Even though it cannot help you much at the moment, it's good to understand that such things as "Debug mode" or "Release mode" do not exist. "Debug" and "Release" are no more then configuration which can have any names. But the configurations are different. In one of the configurations, tracing can be is disabled.
—SA

3 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)

mbue · Answer 1 · 2013-04-23T12:03:00

Solution 2

Goto the code line where the ASSERT is raised. this maybe the BOOL CWnd::ShowWindow(int nCmdShow) function. Set a break point (F9) and run the program (debug). At the first hit or some else the window handle may be invalid. Check the call stack and avoid the call of ShowWindow with an invalid window handle.
Regards.

Posted 23-Apr-13 12:03pm

mbue

Comments

weirdProgrammer-2 25-Apr-13 8:29am

it happens in my CMainFrame constructor actually :S nothing major happening there! But something is wrong, unable to narrow it down at the moment

KarstenK · Answer 2 · 2013-04-22T22:35:00

Solution 1

delete all temp and build files and make a "rebuild all". Sometimes is an resource ID conflict the problem.

Or you must debug in the MFC-stuff :mad:

Posted 22-Apr-13 22:35pm

KarstenK

kevin lang · Answer 3 · 2013-04-24T15:20:00

Solution 3

Maybe problem In ID.maybe maybe.

Posted 24-Apr-13 15:20pm

kevin lang