Debug assertion failed in occcont.cpp file
-
Hello Folks, Can anyone please help me to solve this runtime issue I am facing while running the application in debug mode? the error is as follows: Debug Assertion Failed! Program: C:\WINDOWS\SYSTEM32\mfc140ud.dll File: f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\occcont.cpp Line: 925 For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts. The application is breaking at**
ASSERT(IsWindow(pTemp->m_hWnd));
**line in occcont.cpp file. Thanks in advance.
-
Hello Folks, Can anyone please help me to solve this runtime issue I am facing while running the application in debug mode? the error is as follows: Debug Assertion Failed! Program: C:\WINDOWS\SYSTEM32\mfc140ud.dll File: f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\occcont.cpp Line: 925 For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts. The application is breaking at**
ASSERT(IsWindow(pTemp->m_hWnd));
**line in occcont.cpp file. Thanks in advance.
It means that window handle (pTemp->m_hWnd) is NULL. So this window does not exist. Look at the call stack to find which line of your code causes this assertion failure.
-
Hello Folks, Can anyone please help me to solve this runtime issue I am facing while running the application in debug mode? the error is as follows: Debug Assertion Failed! Program: C:\WINDOWS\SYSTEM32\mfc140ud.dll File: f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\occcont.cpp Line: 925 For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts. The application is breaking at**
ASSERT(IsWindow(pTemp->m_hWnd));
**line in occcont.cpp file. Thanks in advance.
It is a reasonable guess that
pTemp->m_hWndis not a valid Window handle. How that came about is impossible to guess. You need to use your debugger to gather more diagnostic information. Also there is some information at Debug Assertion in occcont.cpp Line: 926[^] which may help. But either way this looks to be a Microsoft problem, so you should report it (with full details) to them.