Debugging and profiling: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 17: | Line 17: | ||
Please see [[Gprof | Gprof page]] | Please see [[Gprof | Gprof page]] | ||
== PGI Profiler ( | == PGI Profiler (pgprof) == | ||
Please see [[Pgprof | Pgprof page]] | Please see [[Pgprof | Pgprof page]] | ||
== Nvidia command-line profiler (nvprof) == | |||
Please see [[Nvprof | nvprof page]] | |||
== Nvidia | == Nvidia Visual Profiler (nvvp) == | ||
==Valgrind== | ==Valgrind== | ||
Please see [[Valgrind | Valgrind page]] | Please see [[Valgrind | Valgrind page]] |
Revision as of 18:03, 30 November 2018
This article is a draft
This is not a complete article: This is a draft, a work in progress that is intended to be published into an article, which may or may not be ready for inclusion in the main wiki. It should not necessarily be considered factual or authoritative.
The Compute Canada national clusters offer a variety of debugging and profiling tools, both command line and those with a graphical user interface, whose use requires an X11 connection. Note that debugging sessions should be conducted using an interactive job and not run on the login node.
GNU Debugger (gdb)
Please see GDB page
PGI Debugger (pgdb)
ARM Debugger (ddt)
Please see the ARM software page.
GNU Profiler (gprof)
Please see Gprof page
PGI Profiler (pgprof)
Please see Pgprof page
Nvidia command-line profiler (nvprof)
Please see nvprof page
Nvidia Visual Profiler (nvvp)
Valgrind
Please see Valgrind page