|Valgrind 3.3 - Advanced Debugging and Profiling for GNU/Linux applications|
by J. Seward, N. Nethercote, J. Weidendorfer and the Valgrind Development Team
Paperback (6"x9"), 164 pages
RRP £12.95 ($19.95)
5.8.3 Controlling the MPI wrapper library
Environment variable ‘MPIWRAP_DEBUG’ is consulted at startup. The default behaviour is to print a starting banner
valgrind MPI wrappers 16386: Active for pid 16386 valgrind MPI wrappers 16386: Try MPIWRAP_DEBUG=help for possible options
and then be relatively quiet.
You can give a list of comma-separated options in ‘MPIWRAP_DEBUG’. These are
- ‘verbose’: show entries/exits of all wrappers. Also show extra debugging info, such as the status of outstanding ‘MPI_Request’s resulting from uncompleted ‘MPI_Irecv’s.
- ‘quiet’: opposite of ‘verbose’, only print anything when the wrappers want to report a detected programming error, or in case of catastrophic failure of the wrappers.
- ‘warn’: by default, functions which lack proper wrappers are not commented on, just silently ignored. This causes a warning to be printed for each unwrapped function used, up to a maximum of three warnings per function.
- ‘strict’: print an error message and abort the program if a function lacking a wrapper is used.
If you want to use Valgrind's XML output facility (‘--xml=yes’), you should pass ‘quiet’ in ‘MPIWRAP_DEBUG’ so as to get rid of any extraneous printing from the wrappers.
|ISBN 0954612051||Valgrind 3.3 - Advanced Debugging and Profiling for GNU/Linux applications||See the print edition|