Intel Software Network articles feed http://software.intel.com/en-us/articles/intel-thread-checker-for-windows-kb/known-issues/ en-us Can’t create a new advanced build activity in Microsoft* Visual Studio* 2008 Environment:

Microsoft* Visual Studio* 2008

Intel (R) VTune(TM) Performance Analyzer v9.1 Update 2 with Intel(R) Thread Profiler 3.1 Update 12

Intel(R) Thread Checker 3.1 Update 12

Intel(R) Parallel Studio, Initial Release

 

Problem:

The user installed VTune(TM) Performance Analyzer with Intel(R) Thread Profiler, Intel(R) Thread Checker first, then installed Intel(R) Parallel Studio. The icons of VTune(TM) Analyzer and other tools will be hidden in Toolbar's Options due to limited length of Toolbar. However if the user opened a solution and built project(s), then click on "Tuning Browser" tab, the user can't create a new advanced build activity since the icon was grayed.

Root-cause:

This is an unexpected error of the integration of Microsoft* Visual Studio* after installing Intel(R) Parallel Studio. For example, when the user has no solution file opened, all icons of tools should be inactive; When the user opens a new solution file, all icons of Intel(R) Parallel Studio are active, but some icons of old tools are inactive.

icon-grayed.bmp 

Resolution:

  1. Click on "Tuning Browser" tab first
  2. Click on "Solution Explorer" tab
  3. Click on "Tuning Browse" tab again.
  4. Click on the project in "Tuning Browser" window

The icon of "Advanced Activity Build" should be active.

icon-on.bmp

]]> http://software.intel.com/en-us/articles/cant-create-a-new-advanced-build-activity-in-microsoft-visual-studio-2008 Thu, 06 Aug 2009 02:22:15 -0700 http://software.intel.com/en-us/articles/cant-create-a-new-advanced-build-activity-in-microsoft-visual-studio-2008#comments http://software.intel.com/en-us/articles/cant-create-a-new-advanced-build-activity-in-microsoft-visual-studio-2008 Intel® Thread Checker for Windows* Knowledge Base Intel® Thread Profiler for Windows* Knowledge Base Intel® VTune™ Performance Analyzer for Windows* Knowledge Base Boxed Product Packages NOT Updated All
Q: 
I have purchased some software products with boxed edition. However, I find their packages are not the same as what they look like from Intel® Business Exchange software download store. Did I purchase wrong/old products?

A: 
No, you didn't. I believe you have purchased the right product and the latest version. We are sorry to get you confused. 
This is because not all of the packages have been updated for the boxed edition at the same time.

]]> http://software.intel.com/en-us/articles/packages-not-updated Fri, 15 May 2009 00:05:29 -0700 http://software.intel.com/en-us/articles/packages-not-updated#comments http://software.intel.com/en-us/articles/packages-not-updated Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Cluster Toolkit for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Integrated Performance Primitives Knowledge Base Intel® Math Kernel Library Knowledge Base Intel® Software Development Products Registration Center Knowledge Base Intel® Thread Checker for Linux* Knowledge Base Intel® Thread Checker for Windows* Knowledge Base Intel® Thread Profiler for Windows* Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Intel® VTune™ Performance Analyzer for Linux* Knowledge Base Intel® VTune™ Performance Analyzer for Windows* Knowledge Base Intel® Thread Checker for Linux* - Execution Speed and Memory Usage

Page Contents:


Why does my software run so slow and/or use so much memory when run with Intel® Thread Checker?
Intel® Thread Checker uses dynamic analysis as your threading software executes. As your software runs, Thread Checker uses instrumentation to monitor each thread, including the threading APIs used and memory accesses. Therefore Thread Checker uses more memory due to the instrumentation and significantly slows down the execution of any software.

For this reason, it is critical to reduce the workload of your software before running it under Thread Checker. Reducing the workload may speed up analysis of the software and may reduce the memory used.

About Workload Reduction: What does workload reduction mean?
This is a reduction in the amount of work your program performs. It might include reducing the amount of data your program processes and/or reducing the amount of processing your program performs on each piece of data.

Some examples of work-load reduction include:

  • Processing a 32x24 pixel image instead of a 1920x1440 pixel image. If there is a threading error within the loops that process the image, it does not provide you with any more information to find the same error thousands or millions of times. Finding a threading error a few (tens or hundreds) times is sufficient and makes you more productive.

  • Minimize the number of times you process each piece of data by reducing the loop iterations. Your software does not need a lot of accuracy when run under Intel® Thread Checker. After all, the goal is to find threading errors and not to get accurate results.

  • Minimize the update rates and/or length. Try using only one second of video, or reduce the update rate of the display to once per second instead of thirty or more updates a second.

About Workload Reduction: What kind of workload reduction should I use?
You should use as much workload reduction as possible while still being sure that you're executing the code that you want checked. Intel® Thread Checker uses dynamic analysis when executing your software. If section of your code is not executed, Thread Checker cannot give you diagnostics about the not-executed code. Where possible, you should try using multiple short runs over different code paths.

]]> http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-execution-speed-and-memory-usage Fri, 19 Sep 2008 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-execution-speed-and-memory-usage#comments http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-execution-speed-and-memory-usage Software Products General Intel® Thread Checker for Windows* Knowledge Base Intel® Thread Checker - Software Defects [ITT_SWDEFECTS_0405.PDF]

The document (linked below) identifies the known issues relating to the Intel® Thread Checker and identifies available workarounds.

iconITT_SWDEFECTS_0405.PDF
Size: 72101 bytes
Date: 04/24/05

Note: PDF Files require Adobe Acrobat* Reader†



† This link will take you off of the Intel Web site. Intel does not control the content of the destination Web Site.

]]> http://software.intel.com/en-us/articles/intel-thread-checker-software-defects-itt_swdefects_0405pdf Fri, 19 Sep 2008 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-thread-checker-software-defects-itt_swdefects_0405pdf#comments http://software.intel.com/en-us/articles/intel-thread-checker-software-defects-itt_swdefects_0405pdf Software Products General Intel® Thread Checker for Windows* Knowledge Base Intel® Thread Checker for Windows* - Product Limitations

This product already contains the Intel® VTune™ Performance Analyzer Patch for Intel® Pentium® Processor Extreme Edition and Intel® Pentium® D Processor (vpa_7.2_ppl.zip). Installing any patch that requires manual copying of files regardless of version number, could potentially overwrite newer versions of these files. Please contact customer support if you wish to install a patch that requires manual file copying.

The binary instrumentation technology used by the Intel® Thread Checker can because some applications to change behavior or terminate abnormally. In this case, you may be able to complete the analysis after lowering the instrumentation levels of problematic modules.

The Intel Thread Checker does not detect threading errors for threads and synchronization objects shared across processes (executables).

The Intel Thread Checker cannot analyze processes that are already running. You must either specify the executable as the application to launch, or specify it as a module of interest and then launch it manually when prompted.

The Intel Thread checker support analysis of only native binaries and does not support intermediate executable representations intended for managed runtime environments.

Source and binary instrumentation of 64-bit applications on processors supporting Intel® EM64T is not supported by this release.

If an application has data race on a global variable, the definition information of the variable will not be available.

The Intel Thread Checker ignores the duration setting in any of the Activity configuration dialogs.

This release does not support Unicode file names.

Use of Stop, Pause/Resume or Cancel to terminate instrumentation or data collection before it completes may cause the VTune™ environment to become unresponsive especially when using the Linux* Remote Agent.

Although Get Tuning Advice (F8 or View menu) may appear to be available when viewing Intel Thread Checker results, it should not be used as it has been found to cause the VTune environment to crash in certain instances.

]]> http://software.intel.com/en-us/articles/intel-thread-checker-for-windows-product-limitations Fri, 19 Sep 2008 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-thread-checker-for-windows-product-limitations#comments http://software.intel.com/en-us/articles/intel-thread-checker-for-windows-product-limitations Software Products General Intel® Thread Checker for Windows* Knowledge Base