5. Tools summary

This section gives a brief description of the available OProfile utilities and their purpose.


This utility lists the available events and short descriptions.


This is the recommended program for collecting profile data, discussed in Section 1, “Using operf.


Used for controlling OProfile data collection in legacy mode, discussed in Section 2, “Using opcontrol.

agent libraries

Used by virtual machines (like the Java VM) to record information about JITed code being profiled. See Section 3, “Setting up the JIT profiling feature”.


This is the main tool for retrieving useful profile data, described in Section 2, “Image summaries and symbol summaries (opreport)”.


This utility can be used to produce annotated source, assembly or mixed source/assembly. Source level annotation is available only if the application was compiled with debugging symbols. See Section 3, “Outputting annotated source (opannotate)”.


This utility can output gprof-style data files for a binary, for use with gprof -p. See Section 5, “gprof-compatible output (opgprof)”.


This utility can be used to collect executables, debuginfo, and sample files and copy the files into an archive. The archive is self-contained and can be moved to another machine for further analysis. See Section 6, “Analyzing profile data on another system (oparchive)”.


This utility converts sample database files from a foreign binary format (abi) to the native format. This is useful only when moving sample files between hosts, for analysis on platforms other than the one used for collection. See Section 7, “Converting sample database files (opimport)”.