VA_X.dll file version 10.0.1244.0 Licensed to: VA X: [email protected] (1-user license) Support ends 2005.07.08 VA.NET 7.1: VAOpsWin.dll version 1.0.0.44 DevEnv.exe version 7.10.3077.0 msenv.dll version 7.10.3077.0 Font: Courier New 13(Pixels) Comctl32.dll version 5.82.2800.1106 WindowsNT 5.1 Build 2600 Service Pack 1 Single processor
Platform: Stable Includes: c:\\program files\\microsoft visual studio .net 2003\\vc7\\include; c:\\program files\\microsoft visual studio .net 2003\\vc7\\atlmfc\\include; c:\\program files\\microsoft visual studio .net 2003\\vc7\\PlatformSDK\\include\\prerelease; c:\\program files\\microsoft visual studio .net 2003\\vc7\\PlatformSDK\\include; c:\\program files\\microsoft visual studio .net 2003\\sdk\\v1.1\\include;
Library Includes: c:\\program files\\microsoft visual studio .net 2003\\vc7\\atlmfc\\src\\mfc; c:\\program files\\microsoft visual studio .net 2003\\vc7\\atlmfc\\src\\atl; c:\\program files\\microsoft visual studio .net 2003\\vc7\\crt\\src;
Other Includes:
When I attemp to find text (ctrl+f or through tool bar) studio bombs complaining about a runtime error in devenv.exe R6025 pure virtual function call.
I reinstalled studio and it still bombed. I reinstalled VAX and it still bombed. I removed VAX and the problem went away.
Also, there are a number of tmp files in the directory of the file being viewed. They include VA_Usage, VACPP_, VaCCPA->VaCPPZ. All except the Usage file has 0 size. The usage file has a row of 12 zeros.
Also getting crash when moving between header and cpp file for the second time. So, if I open a cpp file, I can jump to the header. But trying to move back to the cpp file causes the crash. Likewise, if I open the header, I can jump to the cpp but not back to the header.
Not sure if this is new because in the build I installed today. Possible (even probable) that it was doing it in the other version and I didn't notice or use the feature.
We think the problem is in a MS DLL that either VA X or the IDE references.
There are numerous reports on the bug with various applications. A search on Google for the error tells us this.
We believe the error is fixed in the latest builds of MS platforms. Can you make sure you have the latest service packs for your OS? If we recall correctly, the latest service pack for NT 5.1 is SP 4.
Topic Locked
Posted - Jan 28 2005 : 3:08:05 PM
