| June 13, 2010 12:00 AM PDT | |
Intel(R) 20 Questions Contest: Question #6
Question:
Intel® Parallel Inspector: How many source views does Intel(R) Parallel Inspector/"Threading errors" generate when you double-click on one of the data races found and listed as a problem set?
Correct Answer:
2
Details:
For each threading or memory error that Intel(R) Parallel Inspector finds, it displays high-level information first. The top window of the first view is the list of Problem Sets. The bottom window shows Observations for the currently selected Problem Set (see Figure 1). Observation is a fact about source code related to the problem. When Intel Parallel Inspector finds a data race (Problem), there will be at least two Observations related to it showing source file name(s) and line numbers where two or more threads were accessing/modifying unprotected shared data. You could get a quick look at the code snippet for any Observation by clicking on the '+' near the Observation's ID, or you could double click on the problem and Intel Parallel Inspector will show you two source and Call Stack views (Figure 2). After analyzing all the Observations you should be able to understand the Problem completely and know how to fix it - just double-click on any code line in one of the Intel Parallel Inspector source views and you'll be taken to the Microsoft* Visual Studio editor: change your code (e.g. add synchronization to eliminate the data race) and re-run Intel(R) Parallel Inspector to make sure all symptoms caused by the Problem are gone.
If you'd like to learn more about Intel(R) Parallel Inspector usage methodology and configuration options please read Getting Started Guide or visit Intel Parallel Inspector's home page to learn more.
Figure 1:
Figure 2:
For more complete information about compiler optimizations, see our Optimization Notice.
