Debug information crashes my app :(
-
for some reason my application fails to start and gets this message ... Debug Assertion failed! Program: blah blah blah File: objcore.cpp Line 43 When I rebuild all I see warnings C786: '...' : identifier was truncated to '255' characters in the debug information. I really don't care about the debug information. Why would debug information cause my application to fail?:eek: Please help!
-
for some reason my application fails to start and gets this message ... Debug Assertion failed! Program: blah blah blah File: objcore.cpp Line 43 When I rebuild all I see warnings C786: '...' : identifier was truncated to '255' characters in the debug information. I really don't care about the debug information. Why would debug information cause my application to fail?:eek: Please help!
You've got bugs ... (assuming it's a MFC application) When the application crashes right at the beginning, it can be that one of the main resource ID or resource is corrupted or wrong. put a break point in InitInstance, or any other early called function and trace the problem. Are you sure the warning is not C4786 ? if it is, then, it might be STL naming demangling ( with all the template stuff ) It's a level 1 warning, and can be left alone; or can be removed with
#pragma warning( disable : 4786 )
before including stl headers. Max.
Maximilien Lincourt For success one must aquire one's self
-
for some reason my application fails to start and gets this message ... Debug Assertion failed! Program: blah blah blah File: objcore.cpp Line 43 When I rebuild all I see warnings C786: '...' : identifier was truncated to '255' characters in the debug information. I really don't care about the debug information. Why would debug information cause my application to fail?:eek: Please help!
Diagnostic of the problem is incorrect. If you run debug version (you do) and you use ASSERT in your code (you do) you will get the wonderful message. Example: ASSERT(nValue > 0); //if nValue <= 0 you will see dialog similar to the one you see. Second item compilation warnings could be safely ignored
-
Diagnostic of the problem is incorrect. If you run debug version (you do) and you use ASSERT in your code (you do) you will get the wonderful message. Example: ASSERT(nValue > 0); //if nValue <= 0 you will see dialog similar to the one you see. Second item compilation warnings could be safely ignored
-
Thanks, It looks like my assert is failing in the call to SetRegistryKey? I don't rememeber writting this part of the code? How would my code cause this bug? Thanks