Generating Profile Data

After you've recompiled with the appropriate flags set, you'll need to exercise your software in order to generate the profile data for Imagix 4D to examine.

This is done by running your executable, using whatever test cases you wish to examine. As you run your executables, results are automatically captured into the .gcda/.da and gmon.out files (gcc), .d and gmon.out files (native Unix) or .pbt files (Visual C++).

If you're running Imagix 4D on the same platform where you ran your executables, Imagix 4D can collect the profile data directly from the resulting data files. Imagix 4D uses the native tools available on the platform, such as gprof or some of the Microsoft Visual C++ utilities, to help process the data files.

If however you wish to perform cross-platform analysis of the profile data, Imagix 4D is still able to load in the data. In this case, you need to do some initial processing of the run-time data files on the executable's native platform. Imagix 4D is then able import the intermediate results on whatever platform it is running on.

The post-processing necessary depends on the type of profile data you have generated. The appropriate commands can be issued from the command line.

For gcov data (for each .gcda or .da file):

gcov -b sourcefilename.gcda
For gprof data (gmon.out):

gprof -b executable gmon.out > results_file
For profile data (executable_rootname.pbt):

plist /t executable_rootname > results_file
No post-processing is necessary for tcov data (.d files). Refer to the gcov man page, gprof man page or your Microsoft Visual C++ User Guide for further information.