Debugging Memory Problems with MemoryScape : Chapter 4 Creating Programs for Memory Debugging : Setting Up MPI Debugging Sessions : Debugging MPICH Applications : Attaching to an MPICH Job

Attaching to an MPICH Job
MemoryScape lets you to attach to an MPICH application even if it was not started under MemoryScape’s control. These processes, however, much have previously been linked with the MemoryScape agent. See for Linking Your Application with the Agent” for details.
To attach to an MPICH application:
1
Select Attach to running program from the Add Programs to Your MemoryScape Session screen. You are now shown processes that are not yet owned.
2
3
On an IBM SP with the ch_mpi device, attach to the poe process that started your job. For details, see Starting MemoryScape on a PE Program”. The following figure shows this information.
*
Normally, the first MPICH process is the highest process with the correct program name in the process list. Other instances of the same executable can be:
*
The p4 listener processes if MPICH was configured with ch_p4.
*
*
Additional slave processes if MPICH was configured with ch_p4 and has a file that places multiple processes on the same computer.
4
After you attach to your program’s processes, MemoryScape asks if you also want to attach to slave MPICH processes. If you do, press Return or choose Yes. If you do not, choose No.
If you choose Yes, MemoryScape starts the server processes and acquires all MPICH processes.
In some situations, the processes you expect to see might not exist (for example, they may crash or exit). MemoryScape acquires all the processes it can and then warns you if it can not attach to some of them. If you attempt to dive into a process that no longer exists (for example, using a message queue display), MemoryScape tells you that the process no longer exists.

Rogue Wave Software, Inc.
Voice: (303) 473-9118
rwonlinedocs@roguewave.com