Debugging Sun MPI Programs

If you are going to use Prism to debug a Sun MPI program, use the -np option with mprun to specify how many processes are to be started. For example,

% prism -np 4 a.out

When you use the -np option, you can also use other Prism options, such as -p, to determine where the job's processes are to run and how they are mapped onto nodes. For example,

% prism -p part0 -np 4 a.out

starts Prism as well as the message-passing program a.out on the partition part0. Client Prism processes are also started with each of the a.out processes. They receive instructions from and return information to the master Prism daemon that is started by mprun.

You can attach to a running Sun MPI program by specifying its job ID after the name of the executable program. For example,

% prism -np 1 a.out 462

You can find out the job ID of a program by issuing the mpps command or by using the -J option to mprun.

The setting of the MPRUN_FLAGS environment variable applies to both mprun starting Prism and to Prism starting the parallel processes. This means that the default options are likely to be incorrect for one or the other, since you would typically want to start Prism on one node in a shared partition, and the Sun MPI processes on multiple nodes, possibly in a dedicated partition.