Collecting Trace Files without fgtrun Script
You can choose to collect traces without the
fgtrun
script if you do not want to launch your application from a Visual Studio* command prompt or Linux* terminal. In this case, follow the steps below to collect and convert trace files manually.
These steps do not outline steps required to capture symbol resolution information.
- Set paths to the collector libraries.Set up or update the environment variables shown below. For Windows* systems, specify also the proper version of the Microsoft Visual Studio* compiler (vc12,vc14, orvc14.1).Operating SystemEnvironment VariableDefault ValueDescriptionWindows*INTEL_LIBITTNOTIFY32..\fgt\windows\bin\ia32\<vc version>\fgt.dll32-bit collector libraryINTEL_LIBITTNOTIFY64..\fgt\windows\bin\intel64\<vc version>\fgt.dll64-bit collector libraryINTEL_ITTNOTIFY_GROUPSall;Trace events from all groupsLinux*INTEL_LIBITTNOTIFY32../fgt/linux/lib/ia32/cc4.8_libc2.19_kernel3.13.0/libfgt.so32-bit collector libraryINTEL_LIBITTNOTIFY64../fgt/linux/lib/intel64/cc4.8_libc2.19_kernel3.13.0/libfgt.so64-bit collector libraryINTEL_ITTNOTIFY_GROUPSall;Trace events from all groupsmacOS*INTEL_LIBITTNOTIFY32../fgt/macos/lib/ia32/osx10.12.6_kernel16.7.0/libfgt.dylib32-bit collector libraryINTEL_LIBITTNOTIFY64../fgt/macos/lib/intel64/osx10.12.6_kernel16.7.0/libfgt.dylib64-bit collector libraryINTEL_ITTNOTIFY_GROUPSall;Trace events from all groupsIf you want the Microsoft Visual Studio* IDE to use the environment variables set in a Microsoft Visual Studio command prompt, you can launch the Visual Studio* IDE from the command prompt using the following command:devenv /useenv
- Run the application.If your paths are set up correctly, the application generates one or more files that start with_fgt. There is one file per thread that participates in executing the parallelism in the application. So, for example, if two threads participate in the execution of the flow graph, your run generates two files:_fgt.0and_fgt.1, with an autogenerated folder in the format_fga_YYYYMMDD_HHMMSSaccording to its creation (for example,20191111_1111).
- Convert the trace files to GraphML* and TraceML* format.Convert the_fgtbinary files to the XML format understood by the Flow Graph Analyzer tool using thefgt2xml.execonverter in the directory containing the folder with the trace files:fgt2xml.exe <desired_name>This converter scans the current directory for all_fgtfiles within the most recent folder according to its name and generates two output files:desired_name.graphmlanddesired_name.traceml.