09-24-2004 01:41 AM
looking for a hint on how to use vtune's call graph featurewith an MPI app where:
mpiexec -np 1 program
and the program was compiled and linked with -Zi, /DEBUG and /fixed;no
platform=xp pro sp2, ifort 8.1, andmpich2 (09/04 distribution).
The program process id doesn't appear in a process table (ps in a bash shell).
09-28-2004 12:15 AM
I'm checking on your question, but you should check out http://www.intel.com/support/performancetools/vtune/v71/sb/cs-014754-prd1391.htmfor information on a problem with the VTune analyzer on Windows* XP* SP2.
09-28-2004 09:38 PM
You should be able to specify 'mpiexec' as the app to launch and put the rest in the command line arguments field.Then, removempiexec from the modules of interest and add the mpi app as the module of interest.
Let us know if it works!
09-29-2004 10:43 PM
Thanks, Dave. Your suggestion does in fact work right up to and including the xp/SP2 failure that you reference.
Turns out my single node MPI process runs without getting started by mpiexec,so I was able to run vtune directly on the app andstill ran into the call graph/SP2 bug.
Too much work to try to uninstall SP2. Might be easier to add another partition and install a scratch version of SP1.
10-01-2004 12:21 AM
Per the URL I listed earlier, you only need to view some local sampling data after starting the analyzer to workaround the SP2 problem. Just collect a default sampling run of 5 or 10 seconds in your project and always open the results after starting the analyzer. That's what I would do. :-}