Intel® Trace Analyzer and Collector


double VT_timestamp (void)


In contrast to previous versions, this time stamp no longer represents seconds. Use VT_timeofday() for that instead. The result of VT_timestamp() can be copied verbatim and given to other API calls, but nothing else.





LOGFILE-NAME <file name>




Specifies the name for the tracefile containing all the trace data. Can be an absolute or relative pathname; in the latter case, it is interpreted relative to the log prefix (if set) or the current working directory of the process writing it.

Applications Running on Intel® Xeon Phi™ Coprocessor

To generate a trace file from an MPI application running on an Intel® Xeon Phi™ coprocessor, you need to use the Intel® MPI Library, the Intel® Trace Collector libraries, and a compiler that can generate an executable file compatible with the targeted Intel® Many Integrated Core Architecture (Intel® MIC Architecture). Do the following steps to complete these tasks:


Which errors are checked for at runtime is configurable: all errors have a unique name and are categorized in a hierarchy similar to functions. For example, LOCAL:MEMORY:OVERLAP is a local check which ensures that memory is not used twice in concurrent MPI operations. The CHECK configuration option matches against these full names of each supported error and turns it on or off, like this:

Recording Source Location Information

Intel® Trace Collector can automatically record the locations of subroutine calls in the source code. Compile the relevant application modules with support for debugging by using these compiler flags that enable the generation of debug information for Intel® Trace Collector:

mpicc -g -c ctest.c
mpif77 -g -c ftest.c

If your compiler does not support a flag, then search for a similar one.

Subscribe to Intel® Trace Analyzer and Collector