Changes between Version 4 and Version 5 of cypress/Programming/CodeDebugging

Timestamp:

08/20/15 21:29:31 (9 years ago)

Author:

fuji

Comment:

—

cypress/Programming/CodeDebugging

@@ -92 +92 @@
 
 == GDB ==
-[http://www.gnu.org/software/gdb/]
+GDB is the standard debugger.
+[http://www.gnu.org/software/gdb/documentation/]
 
 To debug with '''GDB''', submit an interactive job. [[https://wiki.hpc.tulane.edu/trac/wiki/cypress/using#SubmittingInteractiveJobs|See here]]
@@ -315 +316 @@
 ==34643== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 6 from 6)
 }}}
+
+== Intel® Inspector XE ==
+Memory and Thread Debugger: 
+* Debug memory errors like leaks and allocation errors and threading errors like data races and deadlocks.
+
+==== Setting Environment and Compiling your code ====
+Load module to setup Intel compilers and tools.
+{{{#!bash
+[fuji@cypress1 ~]$ module load intel-psxe/2015-update1
+}}}
+Compiling codes with '-g' option to tells the compiler to generate full debugging information in the object file.
+{{{#!bash
+[fuji@cypress1 ~]$ icc -g -o mytest mytest.c
+}}}
+
+==== Run and Collect Information ====
+Start an interactive job,
+{{{#!bash
+[fuji@cypress1 ~]$ idev
+}}}
+To collect information, run the code, for example,
+{{{#!bash
+[fuji@cypress1 ~]$ inspxe-cl -collect=mi2 -app-working-dir=$PWD -result-dir=$PWD/results $PWD/mytest
+}}}
+
+'''-collect=''' options
+
+Memory error analysis types
+||= mi1 =||  Detect memory leaks ||
+||= mi2 =||  Detect memory leaks and memory access problems ||
+||= mi3 =||  Find locations of memory leaks and memory access problems ||
+
+Threading error analysis_types
+||= ti1 =||  Detect deadlocks ||
+||= ti2 =||  Detect deadlocks and data races ||
+||= ti3 =||  Find locations of deadlocks and data races ||
+
+To show results, for example, 
+{{{#!bash
+[fuji@cypress1 ~]$ inspxe-cl -R problems -r $PWD/results
+}}}
+See [https://software.intel.com/en-us/node/528226 here] for details.
+
+[[Inspector Brief Tutorial]]
+
+== Intel® Advisor XE ==
+Threading design and prototyping tool for software architects:
+* Analyze, design, tune and check your threading design before implementation
+* Explore and test threading options without disrupting normal development
+* Predict threading errors & performance scaling on systems with more cores
+
+=== Survey ===
+Survey the application to determine hotspots. Typically an optimized
+ (non-debug) version of the application is used when surveying an application.
+
+Run and Collect info.
+{{{#!bash
+$ icc -g -O3 mycode.c
+$ advixe-cl --collect survey --project-dir ./advi ./a.out
+}}}
+
+Show report
+{{{#!bash
+$ advixe-cl --report survey --project-dir ./advi ./a.out
+}}}
+
+=== Add Annotations ===
+Add annotations to the application source code, and rebuild the application.
+ Please see the Getting Started Tutorial for more information.
+
+For C/C++
+{{{#!c
+#include "advisor-annotate.h"
+.....
+    ANNOTATE_SITE_BEGIN(sitename1);
+    for ( .... 
+    {
+        ANNOTATE_TASK_BEGIN(taskname1);
+        ...
+        ANNOTATE_TASK_END();
+    }
+    ANNOTATE_SITE_END();
+}}}
+
+Fortran
+{{{#!fortran
+use advisor_annotate
+.....
+call annotate_site_begin(sitename1)
+do .....
+    call annotate_task_begin(taskname1)
+    ....
+    call annotate_task_end()
+enddo
+call annotate_site_end()
+}}}
+
+=== Suitability ===
+Collect suitability data. Note that annotations must be present in the source
+ code for this collection to be successful. Typically an optimized (non-debug) version
+ of the application is used when collecting suitability data.
+
+{{{#!bash
+$ icc -g -O3 mycode.c -I $ADVISOR_XE_2015_DIR/include
+$ advixe-cl --collect suitability --project-dir ./advi ./a.out
+}}}
+
+{{{#!bash
+$ advixe-cl --report suitability --project-dir ./advi ./a.out
+}}}
+
+
+=== Correctness ===
+Collect correctness data. Note that annotations must be present in the source
+ code for this collection to be successful. Typically an application with debug symbols
+ is used when collecting correctness data.
+
+{{{#!bash
+$  icc -g -O0 mycode.c
+$ advixe-cl --collect correctness --project-dir ./advi ./a.out
+}}}
+
+{{{#!bash
+$ advixe-cl --report correctness --project-dir ./advi ./a.out
+}}}
+
+Display a list of annotations present.
+{{{#!bash
+advixe-cl --report annotations --project-dir ./advi ./a.out
+}}}
+Update the application using the chosen parallel coding constructs. Rebuild the application and test.
+
+[[Advisor Brief Tutorial]]
+
+== Intel® VTune™ Amplifier 2015 ==
+* Intuitive CPU & GPU performance tuning, multi-core scalability, bandwidth and more
+* Quick performance insight with advanced data visualization
+* Automate regression tests and collect data remotely 
+
+Compiling codes with '-g' option to tells the compiler to generate full debugging information in the object file.
+{{{#!bash
+[fuji@cypress1 ~]$ icc -g -o mytest mytest.c
+}}}
+
+==== Run and Collect Information ====
+Start an interactive job,
+{{{#!bash
+[fuji@cypress1 ~]$ idev
+}}}
+To collect information, run the code, for example,
+{{{#!bash
+[fuji@cypress1 ~]$ amplxe-cl -collect hotspot ./mytest
+}}}
+This will create a directory like '''r000hs'''.
+
+'''-collect ''' options
+
+||= concurrency =||  Concurrency analysis ||
+||= hotspots =||  Hotspots analysis ||
+||= lightweight-hotspots =||  Lightweight Hotspots analysis ||
+||= locksandwaits =||  Locks and Waits analysis ||
+
+To show results, for example,
+{{{#!bash
+[fuji@cypress1 ~]$ amplxe-cl -report hotspot -r r000hs
+}}}
+
+'''-report ''' options
+
+||= summary =||  Display data for the overall performance of the target. ||
+||= hotspots =||  Display functions with the highest CPU time. ||
+||= wait-time =||  Display Wait time. ||
+||= perf =||  Display performance data for each module of the target. ||
+||= perf-detail =||  Display performance data for each function of the target. ||
+||= callstacks =||  Display CPU or Wait time for call stacks. ||
+||= top-down =||  Display a call tree for your target application and provide CPU and Wait time for each function. ||
+||= gprof-cc =|| Display CPU or wait time in the gprof-like format. ||
+
+[[VTune Brief Tutorial]]