| Author |
 Topic  |
|
|
diavo
Senior Member
Germany
31 Posts |
 Posted - Mar 16 2011 : 10:20:35 AM
|
Hi,
I'm using VA1836. Up to now it worked perfect. Now I installed VTune from Intel. With this Addin installed, VA does not work properly any longer. Some symbols are recognized and colored correctly, others are not recognized until I go to their declarations and parse the file manually. Also switching between header and .cpp does not always work.
If i remove VTune all is fine again.
Is this a known behaviour? |
|
|
feline
Whole Tomato Software
United Kingdom
19004 Posts |
|
|
diavo
Senior Member
Germany
31 Posts |
Posted - Mar 17 2011 : 02:58:26 AM
|
| Intel-? VTuneG?? Amplifier XE 2011 for Windows |
 |
|
|
Luke1410
Senior Member
32 Posts |
Posted - Mar 17 2011 : 06:28:27 AM
|
| Not much of help, but I'm using VTUNE Amplifier XE 2011 [edit] SP1 [/edit] together with VAX 1842 on VS2005 too and do not experience any issues (at least none related to VAX). |
Edited by - Luke1410 on Mar 17 2011 06:37:28 AM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19004 Posts |
Posted - Mar 17 2011 : 6:21:58 PM
|
I have installed VTune along side VA 1836, and so far I am not seeing any problems with VA. Both colouring and alt-o are working correctly for me.
Luke1410 thank you for this, it is good to know that there is not an automatic problem here on all systems.
diavo are you able to reproduce these problems in a new, default test solution?
Have you been able to spot any pattern yet behind the problems? |
zen is the art of being at one with the two'ness |
|
|
|
diavo
Senior Member
Germany
31 Posts |
Posted - Mar 18 2011 : 02:52:34 AM
|
| I think I found the reason. If a remove the 'results' project of VTune from my solution VA seems to work better. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19004 Posts |
Posted - Mar 18 2011 : 4:44:49 PM
|
| I am glad you have found a solution. Is this a good solution for you? |
zen is the art of being at one with the two'ness |
|
|
|
diavo
Senior Member
Germany
31 Posts |
Posted - Mar 21 2011 : 02:52:31 AM
|
| I dont' think this is a solution but a workaround. Why does this extra project confuse VA? Isn't it a bug? |
|
|
|
feline
Whole Tomato Software
United Kingdom
19004 Posts |
Posted - Mar 21 2011 : 3:01:12 PM
|
I have run the profiler here, without setting it up at all, to produce a simple results project. So far I am not seeing any signs of problems with VA. Both Alt-O and colouring are working correctly, I have run several tests on both.
My results project contains a ".amplxe" file, which is not a file extension I recognise, and it is certainly not a file extension I expect VA to be trying to parse.
Do you have other file extensions in your results project? Unless there is something in the results project that VA thinks it should be parsing, I am not sure why this would be having any effect on VA on your system. |
zen is the art of being at one with the two'ness |
|
|
|
diavo
Senior Member
Germany
31 Posts |
Posted - Mar 22 2011 : 07:26:43 AM
|
Ok. What I did now is to create a new win32 solution. This creates me a default win32 application with some files.
Now I start VTUne that creates me a Amplifier XE Results project with a r000cc.amplxe file.
Now I add something like C:\\Qt\\qt-everywhere-opensource-src-4.7.1\\include to the project's include dir.
Now I add #include "QtCore/QtCore" to the test.cpp file.
Now I close the solution and reload it. The new path is not parsed by VA. So all symbols of Qt are unknown.
If I now remove the VTUne project and reload the solution, VA parses the QT path and all symbols are known. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19004 Posts |
Posted - Mar 22 2011 : 1:26:44 PM
|
Thank you for the clear description, I am seeing the same problem here with VA 1836.
Can you please try installing VA 1845, this has fixed this problem for me:
http://www.wholetomato.com/downloads/default.asp
even after deleting and recreating the VTune results project VA is still correctly picking up the additional include directories setting from the main C++ project. |
zen is the art of being at one with the two'ness |
|
|
|
feline
Whole Tomato Software
United Kingdom
19004 Posts |
Posted - Mar 22 2011 : 11:02:17 PM
|
It is possible this was fixed in VA build 1837, from the history page for this build:
Fixed empty Open File in Solution list with Intel Inspector XE 2011 installed. (case=52285) |
zen is the art of being at one with the two'ness |
|
|
|
diavo
Senior Member
Germany
31 Posts |
Posted - Mar 25 2011 : 09:21:12 AM
|
| Ok. In the current release it works. |
|
|
|
jdimatteo
New Member
8 Posts |
Posted - Dec 10 2014 : 11:22:58 AM
|
FYI, installing Intel VTune Amplifier XE 2015 while VAssist is installed seems to break all plugins, including VAssist (and VTune doesn't work either). They are still listed as installed/enabled in the Extension Manager despite not being functional (e.g. the VAssistX menu is missing). Uninstalling VAssist from the Extension Manager and reinstalling VAssist fixed VAssist (as well as other plugins and VTune).
Note that uninstalling VAssist was necessary for me -- simply running the installer again without first uninstalling did not correct the issue. Also, the same exact thing happened to me when I later installed Intel Parallel Studio XE 2015. So the issue seems to be some kind of interaction between VAssistX and Intel VS integration and is repeatable. Perhaps this is entirely Intel's fault, but just documenting this here in case it helps anyone. |
|
|
| |
Topic |
|
Problem with Intel Addins in VS2005
