stat-gui man page

stat-gui - invoke the Stack Trace Analysis Tool GUI.

SYNOPSIS

stat-gui [ OPTIONS ]

where [ OPTIONS ] represents zero or more stat-gui options.

DESCRIPTION

stat-gui is a GUI that drives STAT, the Stack Trace Analysis Tool, and allows you to interactively control the sampling of stack traces from your parallel application. stat-gui is built on stat-view and provides the same call tree manipulation operations. For more on these operations see stat-view.

In addition to the operations provided by stat-view, stat-gui provides a toolbar to control STAT’s operation.

Attach

Attach to your application and gather an initial sample.

ReAttach

Reattach to the parallel application and gather an initial sample.

Detach

Detach from your application.

Pause

Put the application in a stopped state.

Resume

Set the application running.

Sample

Gather and merge a single stack trace from each task in your parallel application. The application is left in a stopped state after sampling.

Sample Multiple

Gather and merge multiple stack traces from each task in your parallel application over time. The application is left in a stopped state after sampling.

stat-gui can also serve as an interface to attach a full-featured debugger such as TotalView or DDT to a subset of application tasks. This interface can be accessed through the “identify equivalence classes” Eq C button, which will pop up the equivalence classes window . You can then select a single representative, all, or none of an equivalence classes’ tasks to form a subset of tasks. The Attach to Subset buttons will launch the specified debugger and attach to the subset of tasks (note, this detaches STAT from the application). The Debugger Options button allows you to modify the debugger path.

OPTIONS

-a, –attach [hostname:]PID

Attach to the parallel job with resource manager [hostname:]PID.

-P, –withpc

Sample program counter values in addition to function names.

-m, –withmoduleoffset

Sample module offset only.

-i, –withline

Sample source line number in addition to function names.

-o, –withopenmp

Translate OpenMP stacks to logical application view

-U, –countrep

Only gather edge labels with the task count and a single representative. This will improve performance at extreme (i.e., over 1 million tasks) scales.

-w, –withthreads

Sample stack traces from helper threads in addition to the main thread.

-y, –withpython

Where applicable, gather Python script level stack traces, rather than show the Python interpreter stack traces. This requires the Python interpreter being debugged to be built with -g and preferrably -O0.

-C, –create arg_list

Launch the application under STAT’s control. All arguments after -C are used to launch the app. Namely, arg_list is the command that you would normally use to launch your application.

-I, –serial arg_list

Attach to a list of serial processes. All arguments after -I are interpreted as processes. Namely, arg_list is a white-space-separated list of processes to attach to, where each process is of the form [exe@][hostname:]PID.

-d, –debugdaemons

launch the daemons under the deubgger

-s, –sleep time

Sleep for time seconds before attaching and gathering traces. This gives the application time to get to a hung state.

-l, –log

Enable debug logging of the FE frontend, BE backend, CP communication process, SW Stackwalker, SWERR Stackwalker on error. Multiple log options may be specified (i.e., -l FE -l BE).

-L, –logdir log_directory

Dump logging output into log_directory. To be used with the –log option.

-M, –mrnetprintf

Use MRNet’s printf for STAT debug logging.

-G, –gdb

Use (cuda-)gdb to drive the daemons. If you are using cuda-gdb and want stack traces from cuda threads, you must also explicitly specify -w.

-Q, –cudaquick

When using cuda-gdb as the BE, gather less comprehensive, but faster cuda traces. Cuda frames will only show the top of the stack, not the full call path. This also defaults to display filename and line number and will not resolve the function name.

AUTHOR

(Written by ) Gregory L. Lee <lee218@llnl.gov>

COPYRIGHT