| T O P I C R E V I E W |
| neil |
Posted - Jun 12 2006 : 04:06:42 AM
My Visual Studio 2003 hangs every time I press Ctrl-Alt-O. This reproducible. It happens every time. It also happens when I click on the icon. I don't have any other add-ins running at the same time.
Any ideas? Thanks.
VA_X.dll file version 10.2.1446.0 built 2006.05.31
Licensed to:
VA.NET 7.1:
VAOpsWin.dll version 1.3.2.4
VATE.dll version 1.0.4.14
DevEnv.exe version 7.10.3077.0
msenv.dll version 7.10.3077.0
Font: Courier New 13(Pixels)
Comctl32.dll version 5.82.2900.2180
WindowsNT 5.1 Build 2600 Service Pack 2
2 processors
Platform: Win32
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;
|
| 9 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Jun 19 2006 : 3:30:02 PM
You said in an earlier post you "never get control of the IDE back." We realize the instance of the IDE in which you try OFIW hangs, but does the 2nd instance? We expect you to be able to break in with a 2nd instance after the hang starts, and use the 2nd instance to get the call stack from the first.
We checked the logs you send and unfortunately, we don't have enough logging in the code for OFIW to determine what the culprit might be.
If your coworkers or another PC does not have the same problem, can you discern what is different in the environments?
Does the hang occur if you restart your IDE and open only a trivial project? A bigger but unrelated project? |
| neil |
Posted - Jun 19 2006 : 04:05:27 AM
No. I don't have any networked files. |
| support |
Posted - Jun 16 2006 : 7:22:54 PM
Do you have any networked files in your project? |
| neil |
Posted - Jun 15 2006 : 04:30:30 AM
Tried rebuilding the symbol database, and deleting the *.ncb files. Neither worked. Still having the problem. |
| beef |
Posted - Jun 14 2006 : 6:31:30 PM
Maybe it isn't VAX, maybe it is VS that hangs upon VAX request? Have you tried to delete the *.ncb file from the project directory? I have the same problem today in VS6, after forcing the IDE to rebuild the ncb file by deleting it, everything works ok. Unfortunately, it took me 4 hours, three VS and dozen VAX reinstalls to figure this :( |
| feline |
Posted - Jun 14 2006 : 6:17:36 PM
can you produce a log file of this happening please, and email it to [email protected] , referencing this thread.
http://www.wholetomato.com/support/faq.html#log
do you have other projects you work on? if so is this problem project specific? is the project very large? by this i mean well over 5,000 files? |
| neil |
Posted - Jun 14 2006 : 11:11:44 AM
Tried the beta version. Still have the problem. I attached to devenv.exe with a second IDE. I clicked the Open File in Workspace button. I never get control of the IDE back. There is nothing in the Call Stack either. All I have is in the output window, which I cleared before trying OFIW. I am working witha project in Release mode.
'devenv.exe': Loaded 'C:\\WINDOWS\\system32\\browseui.dll', No symbols loaded.
The thread 'Win32 Thread' (0x8b8) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x103c) has exited with code 0 (0x0). |
| support |
Posted - Jun 12 2006 : 2:18:28 PM
Try our beta version. Most of the code behind-the-scenes of the OFIW dialog has been reworked.
http://www.wholetomato.com/downloads/VA_X_Setup1522.exe
If you still get a hang, break in with a 2nd instance of the IDE and send us a call stack. |
| rhummer |
Posted - Jun 12 2006 : 09:18:34 AM
have you tried telling VA X to rebuild it's symbol database? It's under the VA X options -> Performance -> Rebuild. |
