| T O P I C R E V I E W |
| Hexagonal |
Posted - Sep 03 2006 : 11:54:46 AM
Error: Visual Assist X
"Open File in Workspace" doesn't work with Intel Compiler integration.
It shows empty list and infinite "Parsing ..." (but doesn't hang environment);
As I found, latest working version is 1432.
Steps to reproduce problem:
- Install Visual Studio 2005;
- Install Intel C++ Compiler 9.1;
- Create any Visual C++ project: File -> New -> Project -> Win32 Console Application;
- Right click on project in solution and choose "Convert to use Intel C++ Project System" (Intel integration
will create *.icproj file near *.vcproj one);
- Install Visual Assist X 1432;
- Choose VAssist -> Open File in Workspace, it will correctly display list of all files in solution;
- Install Visual Assist X, any of latest versions, for example 1533 beta or 1446;
- Choose VAssist -> Open File in Workspace, it will show empty list and "Parsing ...";
|
| 8 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Sep 19 2006 : 02:00:51 AM
Case 2399 is fixed in build 1535. |
| feline |
Posted - Sep 17 2006 : 2:19:03 PM
VA 1535 should be posted in the next couple of days, to the announcements part of the forum, here:
http://www.wholetomato.com/forum/forum.asp?FORUM_ID=18
can you try that build when it is posted, and see if it helps? |
| Hexagonal |
Posted - Sep 15 2006 : 04:41:24 AM
Hello!
When it displays "Parsing..." message, processor load doesn't exceed 2-4 percents.
Sysinternals Process Viewer displays two VA_X.dll threads:
1:
ntoskrnl.exe!KiUnexpectedInterrupt+0x29f
ntoskrnl.exe!ZwYieldExecution+0x5c9
ntoskrnl.exe!KiUnexpectedInterrupt+0x2d6
ntoskrnl.exe!KeWaitForMutexObject+0x1a3
ntoskrnl.exe!NtWaitForSingleObject+0xb7
ntoskrnl.exe!KiReleaseSpinLock+0xb99
ntdll.dll!NtWaitForSingleObject+0xb
ntdll.dll!ZwCreateThread+0xbe
va_x.dll!MigrateDevColor+0xe633d
va_x.dll+0x17ff2
KERNEL32.dll!GetModuleHandleA+0x2b
KERNEL32.dll!lstrcmpiW+0xb7
2:
ntoskrnl.exe!KiUnexpectedInterrupt+0x29f
ntoskrnl.exe!ZwYieldExecution+0x5c9
ntoskrnl.exe!KiUnexpectedInterrupt+0x2d6
ntoskrnl.exe!KeWaitForMutexObject+0x1a3
ntoskrnl.exe!NtWaitForSingleObject+0xb7
ntoskrnl.exe!KiReleaseSpinLock+0xb99
ntdll.dll!NtWaitForSingleObject+0xb
ntdll.dll!ZwCreateThread+0xbe
va_x.dll!MigrateDevColor+0xe633d
va_x.dll+0x17ff2
KERNEL32.dll!GetModuleHandleA+0x2b
KERNEL32.dll!lstrcmpiW+0xb7
|
| feline |
Posted - Sep 10 2006 : 10:16:38 AM
case=2399 |
| sean |
Posted - Sep 08 2006 : 12:30:23 PM
Thanks for the confirmation. The fix will be in the next build. |
| CreatorCray |
Posted - Sep 08 2006 : 12:14:28 PM
Hi there! I have other problem with Intel compiler integration (see http://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=5054)
I'm terribly sorry guys, but I just do some bit of a hack to check your idea about icproj file and whitelist.
I found string "csproj" in file VAssistNET.dll and changed it to "icproj". And it works!
Will wait for next build in impatience... |
| sean |
Posted - Sep 06 2006 : 2:57:26 PM
VA doesn't know about icproj files - will whitelist that extension in the next build since you report that it used to work correctly [case=2399]. (we decided to switch to a whilelist for project types in order to prevent doing things to unknown project types)
|
| support |
Posted - Sep 03 2006 : 1:24:28 PM
Are any of the threads spinning when you see the parsing message? If so, can you get a call stack from it/them? |
