30.01.2013 Views

TotalView Users Guide - CI Wiki

TotalView Users Guide - CI Wiki

TotalView Users Guide - CI Wiki

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Debugging Cray XT Applications<br />

Debugging Cray XT Applications<br />

The Cray XT Series is supported by the <strong>TotalView</strong> x86_64 distribution. This<br />

section describes running applications on Cray XT Catamount. You should<br />

be familiar with this information when running applications on a Cray XT<br />

CNL. The primary difference between the two, and it is a big difference, is<br />

that Cray XT CNL uses aprun to launch programs rather than yod.<br />

Cray XT Catamount<br />

On the Cray XT Catamount, all jobs running on compute nodes are started<br />

with the yod starter program. These jobs do not have to be MPI jobs.<br />

Debugging a program started with yod is similar to debugging any program<br />

using a starter program. In general, you would type:<br />

totalview totalview_args yod –a yod_args<br />

For example:<br />

totalview yod –a –np 4 ./my_prog<br />

Here are some things you should know:<br />

� tvdsvr_rs processes are started for your compute nodes. (This is a process<br />

started by <strong>TotalView</strong> on a remote note that communicates back with<br />

<strong>TotalView</strong>. For more information on this server, see Chapter 4.) yod will<br />

then pass information to <strong>TotalView</strong>, which will then start the servers. If this<br />

does not occur, consult your yod documentation.<br />

� There may be more than one tvdsvr_rs process. <strong>TotalView</strong> will create one<br />

tvdsvr_rs process for each RS_DBG_CLIENTS_PER_SERVER or 64 compute<br />

nodes.<br />

� To attach to a running program, attach to the instance of yod that is<br />

controlling it using normal <strong>TotalView</strong> mechanisms. <strong>TotalView</strong> will automatically<br />

attach to all compute node tasks that are part of the job.<br />

� <strong>TotalView</strong> cannot know how many compute nodes are available, so each<br />

server assumes that it will be serving 64 compute nodes, and asks for a<br />

64-node license. You can override this default by using the<br />

–nodes_allowed tvdsvr command-line option.<br />

If you wish to use a small license (that is, a license for less than 64 processors),<br />

you must use the –nodes_allowed tvdsvr command-line option.<br />

The argument to this option specifies how many nodes the server supports<br />

and how many licenses it needs. Because this is a tvdsvr_rs command-line<br />

option, you must add it into the server launch string.<br />

You can also use the –nodes_allowed server launch string option along with<br />

the RS_DBG_CLIENTS_PER_SERVER environment variable to increase the<br />

number of compute nodes each server will serve (and the number of Cray<br />

licences it asks for). However, we do not recommend that you set this<br />

server launch string option to a value greater than 256. (Note that you only<br />

need set this variable if RS_DBG_CLIENTS_PER_SERVER is greater than 64.)<br />

144 Chapter 7: Setting Up Parallel Debugging Sessions

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!