TotalView - Revision history

Christian-iwainsky-2ee8@tu-darmstadt.de at 10:20, 13 January 2022

2022-01-13T10:20:55Z

Paul-kapinos-e26d@rwth-aachen.de at 06:30, 12 June 2020

2020-06-12T06:30:54Z

Daniel-schurhoff-de23@rwth-aachen.de at 08:26, 5 September 2019

2019-09-05T08:26:31Z

Fabian-orland-a681@rwth-aachen.de: added RWTH site-specific information

2019-08-23T07:20:34Z

added RWTH site-specific information

Fabian-orland-a681@rwth-aachen.de at 15:39, 21 August 2019

2019-08-21T15:39:29Z

Fabian-orland-a681@rwth-aachen.de at 09:09, 21 August 2019

2019-08-21T09:09:19Z

Fabian-orland-a681@rwth-aachen.de: Created page with "TotalView is a debugging software designed for high-scale HPC applications. It supports debugging serial as well as parallel applications. Supported parallel programming mode..."

2019-08-20T15:42:17Z

Created page with "TotalView is a debugging software designed for high-scale HPC applications. It supports debugging serial as well as parallel applications. Supported parallel programming mode..."

New page

TotalView is a debugging software designed for high-scale HPC applications.
It supports debugging serial as well as parallel applications.
Supported parallel programming models include OpenMP, MPI, OpenACC and CUDA. <br />
This page briefly describes how to debug serial and parallel programs written in C, C++ or Fortran 90/95 using the TotalView debugger.

== Debugging Serial Programs ==

=== Preparation ===
Before debugging the program needs to be compiled with debug information using the '''-g''' flag and without any optimization (-O0 flag).

=== Starting TotalView ===
There are three ways to start debugging your program:
* by starting TotalView with your program as a parameter <syntaxhighlight lang="sh">$ totalview a.out [ -a options ]</syntaxhighlight>
* by starting your program first and then attaching TotalView to it. In this case just start <syntaxhighlight lang="sh">$ totalview</syntaxhighlight>. You will be asked what you would like to debug. Choose ''A running program (attach)'' and look for your already started program.
* by analyzing the core dump after your program crashed using <syntaxhighlight lang="sh">$ totalview a.out <corefile></syntaxhighlight>
If the program requires startup parameters like runtime arguments, environment variables or standard IO these can be set in the ''Process''<math>\rightarrow</math>''Startup Parameters...'' menu. <br />
After starting your programm Total View opens the ''Process Window'' which consists of different parts summarized by the table below:
{| class="wikitable"
|-
| ''Source Pane'' || displays the program's source code
|-
| ''Stack Trace Pane'' || displays the call stack
|-
| ''Stack Frame Pane'' || displays all variables associated with the selected stack routine
|-
| ''Tabbed Pane'' || displays all breakpoints, action points and evaluation points in the ''Action Points'' subpane <br /> displays all (MPI) processes in the ''Processes'' subpane <br /> displays all threads of the current process in the ''Threads'' subpane
|-
| ''Status Bar'' || displays the status of the current process and thread
|-
| ''Toolbar'' || contains all action buttons
|}

=== Breakpoints ===
A breakpoint can easily be set by clicking on a boxed line number of an executable statement in the ''Source Pane''. To remove a breakpoint just click on the corresponding boxed line number again.

← Older revision		Revision as of 08:26, 5 September 2019
Line 1:		Line 1:
		+	[[Category:HPC-Developer]]
	TotalView is a debugging software designed for high-scale HPC applications.		TotalView is a debugging software designed for high-scale HPC applications.
	It supports debugging serial as well as parallel applications.		It supports debugging serial as well as parallel applications.

← Older revision		Revision as of 07:20, 23 August 2019
Line 176:		Line 176:
	In a parallel OpenMP program each thread may have an own copy of a variable. This is the case for ''private'' variables. Hence, the value of such a variable might be different across different threads.		In a parallel OpenMP program each thread may have an own copy of a variable. This is the case for ''private'' variables. Hence, the value of such a variable might be different across different threads.
	In order to examine these values you can dive in a variable to open the ''Variable Window''. There you can select ''View<math>\rightarrow</math>Show Across<math>\rightarrow</math>Threads'' and will get a list of the values for each thread. Alternatively, you can right-click on a variable and select ''Across Threads'' which has the same effect. These values can also be visualized graphically by opening the ''Variable Window'' and selecting ''Tools<math>\rightarrow</math>Visualize''. Note that only one-dimensional arrays or array slices can be visualized in this way and that the thread ID is interpreted as an additional dimension.		In order to examine these values you can dive in a variable to open the ''Variable Window''. There you can select ''View<math>\rightarrow</math>Show Across<math>\rightarrow</math>Threads'' and will get a list of the values for each thread. Alternatively, you can right-click on a variable and select ''Across Threads'' which has the same effect. These values can also be visualized graphically by opening the ''Variable Window'' and selecting ''Tools<math>\rightarrow</math>Visualize''. Note that only one-dimensional arrays or array slices can be visualized in this way and that the thread ID is interpreted as an additional dimension.
		+
		+	== Site-specific notes ==
		+	=== RWTH ===
		+	In order to use TotalView on the RWTH Cluster you need to load the corresponding module using the [[Modules \| module]] system.
		+	The TotalView module is part of the ''DEVELOP'' module group. You can load this group with the following command:
		+	<syntaxhighlight lang="sh">
		+	$ module load DEVELOP
		+	</syntaxhighlight>
		+	If you like to get an overview about the installed Versions use the command:
		+	<syntaxhighlight lang="sh">
		+	$ module avail totalview
		+	</syntaxhighlight>
		+	To load a specific version of the TotalView module type:
		+	<syntaxhighlight lang="sh">
		+	$ module load totalview/<version>
		+	</syntaxhighlight>
		+	By omitting the <code><version></code> the module system will load a default version of the TotalView module.

@@ Line 5: / Line 5: @@
 == Debugging Serial Programs ==
 Before debugging the program needs to be compiled with debug information using the '''-g''' flag and without any optimization (-O0 flag).
@@ Line 79: / Line 77: @@
 === ReplayEngine ===
-Another interesting feature of Totalview is the ReplayEngine.
+Another interesting feature of Totalview is the ReplayEngine which records the program execution. As a result each program state can be restored afterwards. This feature allows to step forward and backwards through the code.

@@ Line 31: / Line 31: @@
 |}
-=== Breakpoints ===
+=== Starting, Stopping and Restarting a program ===
-A breakpoint can easily be set by clicking on a boxed line number of an executable statement in the ''Source Pane''. To remove a breakpoint just click on the corresponding boxed line number again.
+A program can be started by selecting the ''Go'' button and stopped by clicking on the ''Halt'' button in the ''Toolbar''.

@@ Line 4: / Line 4: @@
 Supported parallel programming models include OpenMP, MPI, OpenACC and CUDA. <br />
 This page briefly describes how to debug serial and parallel programs written in C, C++ or Fortran using the TotalView debugger.
 == Debugging Serial Programs ==