Intel® Trace Collector 9.1 Update 2 User and Reference Guide
Before tracing your applications make sure to complete the steps described in the previous section.
To trace an application, use the -trace option of the mpirun command. For example:
$ mpirun -trace -n 4 ./myApp
If you use your own launch scripts, you can use the LD_PRELOAD environment variable to point to the appropriate profiling library (see Product Components) and run the application. For example:
$ export LD_PRELOAD=libVTfs.so $ mpirun -n 4 ./myApp
To trace an application, rebuild it with the -trace option and run it as usual. For example:
$ mpiicc -static_mpi -trace myApp.c -o myApp $ mpirun -n 4 ./myApp
The -trace option links the Intel® Trace Collector library statically. If you wish to link it dynamically, use the following flag sequence: -trace -dynamic_log.
If you wish to specify the profiling library, use the -profile=<profiling_library> option instead of -trace. For the list of available libraries, see Product Components. For example, for the fail-safe tracing library:
$ mpiicc -static_mpi -profile=vtfs myApp.c -o myApp
For more details on the options used, see the Intel® MPI Library documentation.
To trace an application, do the following:
Rebuild your application with the -trace compiler option. For example:
> mpiicc -trace myApp.c
Run the application as usual:
> mpiexec -n 4 myApp.exe
After running your application, a tracefile with the .stf extension will be created. Open this tracefile in Intel® Trace Analyzer to analyze the application behavior. See the Intel® Trace Analyzer User and Reference Guide for details.