VC++ Service Pack 5 Problem?
-
Hello! I just installed Microsoft Visual Studio Service Pack 5, I had Visual C++ 6.0 Standard Edition on my computer already. I opened up one of my programs and ran the program under debug mode and I got an assertion errors saying: Debug Assertion Failed! File: olelink.cpp Line: 85 Upon inspection, line 84-86 of olelink.cpp look like this: // attach the document to the server ASSERT(m_pFactory == NULL || m_pFactory == pFactory); m_pFactory = pFactory; Part of the "Register" function which I think registers an OLE document. "Okay" I'm thinking, maybe just another strange error for which I have to recompile the project because of a service pack. So I recompile the whole project run it again under debug mode, same assertion. I run it under release mode, same error. I restart my computer, run it under debug mode then release mode, same error every single time. So I go into a debug session and step through the code until I hit the assertion where its failing. I check to make sure why its asserting and apparently m_pFactory = 0xffffff, and the program asserts. I have no possible clue WHY it asserts, 0xfffffff is obviously an invalid address, but maybe the program doesn't think its null. I searched everywhere on codeproject, codeguru, microsoft support, nothing on this problem. Does anyone have any idea here? Can you give me a clue or a lead? I would be most grateful, otherwise its looking like I'm going to have to reinstall visual c++ standard edition and avoid service packs for the rest of my life (I don't know why I didn't avoid this one). By the way, I'm running on Windows XP, and my version is Visual C++ 6.0 Standard Edition, and the program I tested was working before I installed service pack 5. Thanks a bunch in advance for anyone who can help me! Sincerely, Alexander Wiseman Est melior esse quam videri It is better to be than to seem Et tu, Microsoft?
-
Hello! I just installed Microsoft Visual Studio Service Pack 5, I had Visual C++ 6.0 Standard Edition on my computer already. I opened up one of my programs and ran the program under debug mode and I got an assertion errors saying: Debug Assertion Failed! File: olelink.cpp Line: 85 Upon inspection, line 84-86 of olelink.cpp look like this: // attach the document to the server ASSERT(m_pFactory == NULL || m_pFactory == pFactory); m_pFactory = pFactory; Part of the "Register" function which I think registers an OLE document. "Okay" I'm thinking, maybe just another strange error for which I have to recompile the project because of a service pack. So I recompile the whole project run it again under debug mode, same assertion. I run it under release mode, same error. I restart my computer, run it under debug mode then release mode, same error every single time. So I go into a debug session and step through the code until I hit the assertion where its failing. I check to make sure why its asserting and apparently m_pFactory = 0xffffff, and the program asserts. I have no possible clue WHY it asserts, 0xfffffff is obviously an invalid address, but maybe the program doesn't think its null. I searched everywhere on codeproject, codeguru, microsoft support, nothing on this problem. Does anyone have any idea here? Can you give me a clue or a lead? I would be most grateful, otherwise its looking like I'm going to have to reinstall visual c++ standard edition and avoid service packs for the rest of my life (I don't know why I didn't avoid this one). By the way, I'm running on Windows XP, and my version is Visual C++ 6.0 Standard Edition, and the program I tested was working before I installed service pack 5. Thanks a bunch in advance for anyone who can help me! Sincerely, Alexander Wiseman Est melior esse quam videri It is better to be than to seem Et tu, Microsoft?
0xfffffff is not NULL. 0x0 is NULL. That is why the assert is firing. How it got to that state, is an entirely different question. You could try to trace it back and see where it gets this value, you will probably find it happens in one of the dlls that were replaced by the service pack. Is it possible that one of the XP dlls got reverted to an earlier version when the SP 5 was installed? I use VC 6 with SP5 on my XP Home edition. I haven't seen this problem, but I haven't used it much in that environment yet. Good Luck, Bill
-
0xfffffff is not NULL. 0x0 is NULL. That is why the assert is firing. How it got to that state, is an entirely different question. You could try to trace it back and see where it gets this value, you will probably find it happens in one of the dlls that were replaced by the service pack. Is it possible that one of the XP dlls got reverted to an earlier version when the SP 5 was installed? I use VC 6 with SP5 on my XP Home edition. I haven't seen this problem, but I haven't used it much in that environment yet. Good Luck, Bill
Bill, Thanks for your response. I know 0xfffffff is not NULL, but I'm wondering why the stupid variable wasn't initialized to NULL to satisfy the ASSERTION condition. I believe that you are correct in saying that one of the XP dlls got changed by the service pack, but I fail to see why Microsoft did not say anything about it in their report of the fixes. Anyway, if someone else comes up with this problem I'll look into again, I uninstalled then reinstalled Microsoft Visual C++ Standard Edition to start from square one, didn't take too long and everything is back to normal now, so I'm in business. But I definitely want to know what the heck happened... Thanks for your help! Sincerely, Alexander Wiseman Est melior esse quam videri It is better to be than to seem