# Overview

The gprof profiler includes the following features:

- It operates as a stand-alone text-based application, and it is
compatible with the GNU gprof profiler.
- It displays function-level and call-graph profiling information,
which shows the function execution times and caller/callee
relationships in a profiled program.
- It works with any Hexagon target program (stand-alone, RTOS-based,
single- threaded, or multi-threaded).

Note

The profiler performs *post-mortem* processing of the target
application: that is, it is used after the target application has
completed executing.

## Profile data files

The gprof profiler obtains its profiling information from data files
that are generated by the Hexagon simulator. These files are called
gmon files.

For more information on generating profile data files, see the
*Qualcomm Hexagon Simulator User Guide*.

## Profile reports

The profiling information generated by the gprof profiler is
presented in the form of a report which presents the number of cycles
executed in each function, the functions that each function called or
was called by, and how many times each function was called.

Profile reports are generated in plain text format.

## Feedback

If you have any comments or suggestions on how to improve the
profiler (or this document), please send them to:

[support.cdmatech@qti.qualcomm.com](mailto:support.cdmatech%40qti.qualcomm.com)

Last Published: Oct 06, 2026

[Previous Topic
Technical assistance](https://docs.qualcomm.com/bundle/publicresource/80-N2040-29/topics/gprof-profiler-ug-introduction.md) [Next Topic
Use the Profiler](https://docs.qualcomm.com/bundle/publicresource/80-N2040-29/topics/gprof-profiler-ug-use-the-profiler.md)