HP-MPI User's Guide (11th Edition)

Understanding HP-MPI
MPI options
Chapter 3 137
MPI_FLAGS MPI_FLAGS modifies the general behavior of HP-MPI. The
MPI_FLAGS syntax is a comma separated list as follows:
[edde,][exdb,][egdb,][eadb,][ewdb,][l,][f,][i,]
[s[a|p][#],][y[#],][o,][+E2,][C,][D,][E,][T,][z]
where
edde Starts the application under the dde debugger. The
debugger must be in the command search path. See
“Debugging HP-MPI applications” on page 197 for
more information.
exdb Starts the application under the xdb debugger. The
debugger must be in the command search path. See
“Debugging HP-MPI applications” on page 197 for
more information.
egdb Starts the application under the gdb debugger. The
debugger must be in the command search path. See
“Debugging HP-MPI applications” on page 197 for
more information.
eadb Starts the application under adb—the absolute
debugger. The debugger must be in the command
search path. See “Debugging HP-MPI applications” on
page 197 for more information.
ewdb Starts the application under the wdb debugger. The
debugger must be in the command search path. See
“Debugging HP-MPI applications” on page 197 for
more information.
epathdb Starts the application under the path debugger. The
debugger must be in the command search path. See
“Debugging HP-MPI applications” on page 197 for
more information.
l Reports memory leaks caused by not freeing memory
allocated when an HP-MPI job is run. For example,
when you create a new communicator or user-defined
datatype after you call MPI_Init, you must free the
memory allocated to these objects before you call
MPI_Finalize. In C, this is analogous to making calls
to malloc() and free() for each object created during
program execution.