Special debugging arguments


Up: In Case of Trouble Next: p4 Debugging Previous: HP-UX

These are currently undocumented, and some require configure options to have been specified (like -mpipktsize and -chmemdebug). The option -mpiversion is useful for finding out how your installation of mpich was configured and exactly what version it is. The options include:

-mpedbg
If an error occurs, start xterms attached to the process that generated the error. Requires the mpich be configured with -mpedbg and works on only some workstations systems.

-mpiversion
Print out the version and configuration arguements for the mpich implementation being used.


These arguments are provided to the program, not to mpirun. For example, 
   mpirun -np 2 a.out -mpiversion


Up: In Case of Trouble Next: p4 Debugging Previous: HP-UX

p4 Debugging


Up: Special debugging arguments Next: Acknowledgments Previous: Special debugging arguments

If your configuration of mpich used -device=ch_p4, then some of the p4 debugging capabilities are available to you. The most useful of these are the command line arguments to the application program. Thus 

    mpirun -np 10 myprog -p4dbg 20 -p4rdbg 20
results in program tracing information at a level of 20 being written to stdout during execution. For more information about what is printed at what levels, see the p4 Users' Guide [(ref butler-lusk:p4-manual)].


Up: Special debugging arguments Next: Acknowledgments Previous: Special debugging arguments