|
Under certain circumstances, the product may incorrectly identify its version.
On systems running Windows* 2003 Server, Service Pack 1, you may have the following problems when accessing the VTune™ Performance Analyzer help files:
- If you integrate the VTune analyzer with Microsoft* Visual Studio* during installation, links from the VTune analyzer help integrated into Visual Studio to VTune analyzer's chm files do not work.
- If topics in the chm files use Dynamic HTML effects, the Microsoft* Internet Explorer provides a warning message.
To correct this problem, you must adjust the Security settings of the Internet Explorer Internet Options as follows:
- In the Microsoft Internet Explorer, select Tools » Internet Options.
- Click the Security tab.
- Click the Custom Level button.
- Scroll down to the Miscellaneous section.
- Scroll down to the Web sites in less privileged web content zone can navigate into this zone and click the Prompt choice.
- Click OK
Using these settings will not make your other web sites vulnerable. [SCR #25845]
- You cannot view results of an Activity if you move a project manually. Use File » Pack and Go to properly pack and move the files.
- Packed project files issues:
- Compressed packed project files (.vxp) created with VTune analyzer for Linux* version 8.0 or later cannot be unpacked with this product.
- Uncompressed packed project files (.vxp) created with VTune analyzer for Linux version 8.0 or later may not unpack correctly when being unpacked with this product. Uncompressed packed project files created by a future version of the VTune analyzer for Linux should fix this problem. Please check the Release Notes for the future version for details. [SCR#25420]
- In the case where a packed Sampling result does not unpack correctly, the .TB5 file may be viewed by using the Open File menu item.
Projects packed with versions of the VTune analyzer prior to version 6.1 cannot be unpacked with the current version.
You cannot create projects in the %WINDIR%\System32 directory on systems using Itanium® 2 processors.
Function splitting can cause inaccurate results in the sampling view, call graph, or from the Tuning Assistant. A function is split when it has multiple non-contiguous relative virtual address (RVA) ranges. A compiler can generate split functions for a variety of reasons, usually when doing optimizations or for exception handling in C++. For example, using the Intel® C/C++ compiler 7.x and 8.x with the options Qprof_use or Qprof_gen (associated with profile guided optimization) often creates split functions. In addition, some exception handling routines in C++ may create split function. You can, however, tell the Intel(R) C/C++ compiler not to create split functions by using the Qfnsplit- option. A detailed description of this issue follows: [SCR #12424] [SCR #12427]
- When split functions occur from using the Intel(R) C/C++ Compiler, the sampling view feature is impacted. Parts of a symbol are considered as separate symbols. So, in a sampling view there might be a few records for one symbol. The data itself is valid as a sum of all parts.
- When split functions occur from using the Intel(R) C/C++ Compiler, the call graph feature is significantly impacted. The call graph data may be incorrect.
- The Tuning Assistant is only impacted when the user asks for advice at the hotspot or source level. In this case, the advice generated by the Tuning Assistant for split functions may either be non-existent or partial. This behavior exists for split functions that were created by either the Intel C/C++ Compiler or the Microsoft* Visual C/C++* Compiler.
Note: When using the Intel C/C++ compiler Qipo option, symbol information is lost. VTune analyzer features that require symbol information may not work.
- An extremely long delay can occur (creating the impression of a software hang) when opening views containing a large number of entries. Extremely slow response has been reported when a view contains tens of thousands of entries. In one case, a drill down view containing 87,000 entries took over 30 minutes to appear. This is more likely to occur when viewing (sampling) Hotspots by RVA or by Functions, especially when a lot of samples with unique addresses were collected, or when viewing call graph results of a very large module (for example, 250MB module size and symbols).
- The online help contains incorrect links to some of the events for the processor code named Montecito. If you run into this problem, perform a manual search for this event to view its description.
Operating System:
This applies to:
|