Difference between revisions of "GPU621/Striking"

From CDOT Wiki
Jump to: navigation, search
(Progress)
(Progress)
Line 17: Line 17:
 
'''Nov 6th - 13th:'''
 
'''Nov 6th - 13th:'''
 
*There are great resources about Intel Parallel Debugger Extension for Microsoft Visual Studio like below.
 
*There are great resources about Intel Parallel Debugger Extension for Microsoft Visual Studio like below.
# Debugging Threads in Intel Parallel Studio - [[http://www.drdobbs.com/windows/intel-parallel-debugger-extension-for-mi/214502747 Dr Dobbs Article]]
+
# Debugging Threads in Intel Parallel Studio - [[http://www.drdobbs.com/windows/intel-parallel-debugger-extension-for-mi/214502747 Dr. Dobbs Article]]
 
# Intel® Parallel Debugger Extension, Added Aug 2, 2012 - [[https://software.intel.com/en-us/articles/parallel-debugger-extension]]
 
# Intel® Parallel Debugger Extension, Added Aug 2, 2012 - [[https://software.intel.com/en-us/articles/parallel-debugger-extension]]
 
# Intel Parallel Composer Parallel Debugger Extension Tutorial - [[https://www.youtube.com/watch?v=uo3kAhVQUcs Mittie Sylvian's Video]]
 
# Intel Parallel Composer Parallel Debugger Extension Tutorial - [[https://www.youtube.com/watch?v=uo3kAhVQUcs Mittie Sylvian's Video]]
Line 36: Line 36:
 
<tr><td>Callout Letter</td><td>Element Name</td><td>Description</td></tr>
 
<tr><td>Callout Letter</td><td>Element Name</td><td>Description</td></tr>
 
<tr><td>A</td><td>Call Stack Segment or Node</td><td>Contains a series of method contexts for one or more threads. </td></tr>
 
<tr><td>A</td><td>Call Stack Segment or Node</td><td>Contains a series of method contexts for one or more threads. </td></tr>
<tr><td>B</td><td>Blue Highlight</td><td>Presente the call path of the current thread.</td></tr>
+
<tr><td>B</td><td>Blue Highlight</td><td>Present the call path of the current thread.</td></tr>
 
<tr><td>C</td><td>Arrow lines</td><td>Connect nodes to make up the entire call path for the thread(s).</td></tr>
 
<tr><td>C</td><td>Arrow lines</td><td>Connect nodes to make up the entire call path for the thread(s).</td></tr>
 
<tr><td>D</td><td>Tooltip on Node Header</td><td>Shows the ID and user-defined name of each thread whose call path shares this node.</td></tr>
 
<tr><td>D</td><td>Tooltip on Node Header</td><td>Shows the ID and user-defined name of each thread whose call path shares this node.</td></tr>
Line 53: Line 53:
 
<table border="1">
 
<table border="1">
  
<tr><td>[[File:qsort_set1.png|300px|thumb|left|alt qsort_set1]]</td><td></td></tr>
+
<tr><td>[[File:qsort_set1.png|300px|thumb|left|alt qsort_set1]]</td><td>Recursive calling parallel_qsort of spawning parallel_qsort in the first parallel_qsort function which main thread has responible for</td></tr>
 
<tr><td>[[File:qsort_set2.png|300px|thumb|left|alt qsort_set2]]</td><td></td></tr>
 
<tr><td>[[File:qsort_set2.png|300px|thumb|left|alt qsort_set2]]</td><td></td></tr>
 
<tr><td>[[File:qsort_set3.png|300px|thumb|left|alt qsort_set3]]</td><td></td></tr>
 
<tr><td>[[File:qsort_set3.png|300px|thumb|left|alt qsort_set3]]</td><td></td></tr>
Line 63: Line 63:
 
----
 
----
 
* Debugging Tips
 
* Debugging Tips
# Hit F9 at the front of a line to put the break points
+
# Hit F9 at the front of a line to put the breakpoints
 
# Run the program in Debug mode first and then open the windows you need.
 
# Run the program in Debug mode first and then open the windows you need.
 
# Open the windows like Memory, Threads, Parallel Stacks, and Local or Auto.
 
# Open the windows like Memory, Threads, Parallel Stacks, and Local or Auto.
 
# Hit F10 or F11 to run codes line by line
 
# Hit F10 or F11 to run codes line by line
# F9 to put or remove break points
+
# F9 to put or remove breakpoints
  
 
----
 
----

Revision as of 12:29, 8 December 2016

Striking

Our project: Debugging Threads in Intel Parallel Studio

Group Members

  1. Eunju Han [1] Research etc.
  2. Lei(Eric) Zhang [2] (Dropped the course) Research etc.

Progress

Oct 17th:

  1. Picked topic
  2. Picked presentation date.

Oct 20th:

  1. Created Wiki page

Nov 6th - 13th:

  • There are great resources about Intel Parallel Debugger Extension for Microsoft Visual Studio like below.
  1. Debugging Threads in Intel Parallel Studio - [Dr. Dobbs Article]
  2. Intel® Parallel Debugger Extension, Added Aug 2, 2012 - [[3]]
  3. Intel Parallel Composer Parallel Debugger Extension Tutorial - [Mittie Sylvian's Video]

However, Intel Parallel Debugger Extension has been deprecated from the version Intel Composer XE 2013 at the end of 2012. I have noticed this from the Intel User Forum.

Nov 14th - 23th:

  • Links about Debug Multithreaded Applications in Visual Studio
  1. How to: Use the Threads Window
  2. How to: Use the Parallel Watch Window
  3. Using the Parallel Stacks Window
alt text
Callout LetterElement NameDescription
ACall Stack Segment or NodeContains a series of method contexts for one or more threads.
BBlue HighlightPresent the call path of the current thread.
CArrow linesConnect nodes to make up the entire call path for the thread(s).
DTooltip on Node HeaderShows the ID and user-defined name of each thread whose call path shares this node.
EMethod ContextRepresents one or more stack frames in the same method.

Sample code to use debugging

    • Data flow of parallel_qsort
alt qsort_set1
Recursive calling parallel_qsort of spawning parallel_qsort in the first parallel_qsort function which main thread has responible for
alt qsort_set2
alt qsort_set3
alt qsort_set4_1
alt qsort_set4_done
alt dataflow

  • Debugging Tips
  1. Hit F9 at the front of a line to put the breakpoints
  2. Run the program in Debug mode first and then open the windows you need.
  3. Open the windows like Memory, Threads, Parallel Stacks, and Local or Auto.
  4. Hit F10 or F11 to run codes line by line
  5. F9 to put or remove breakpoints


Links about Intel® Parallel Studio XE 2017

  1. link1 Intel® Parallel Studio XE 2017
  2. link2 Intel® Parallel Studio XE 2017
  3. link Intel® Parallel Studio XE Release Notes