The next three chapters explain these steps in greater detail. You must run gprof to analyze the profile data. You must execute your program to generate a profile data file. See section Compiling a Program for Profiling. You must compile and link your program with profiling enabled. Profile information will be generated for that feature. If youĭon't use some feature of your program while it is being profiled, no

Will affect the information that shows up in the profile data. Of your program, it can be used on programs that are too large or tooĬomplex to analyze by reading the source. Since the profiler uses information collected during the actual execution It can also tell you which functions are being called more

Information can show you which pieces of your program are slower than youĮxpected, and might be candidates for rewriting to make your programĮxecute faster. Profiling allows you to learn where your program spent its time and whichįunctions called which other functions while it was executing. Into another language, under the same conditions as for modified versions. Permission is granted to copy and distribute translations of this manual Resulting derived work is distributed under the terms of a permission Manual under the conditions for verbatim copying, provided that the entire Permission is granted to copy and distribute modified versions of this This manual provided the copyright notice and this permission notice Permission is granted to make and distribute verbatim copies of This manual was edited January 1993 by Jeffrey OsierĪnd updated September 1997 by Brent Baccala.Ĭopyright (C) 1988, 1992, 1997, 1998 Free Software Foundation, Inc. We assume that you know how to write, compile, andĮxecute programs. This manual describes the GNU profiler, gprof, and how youĬan use it to determine which parts of a program are taking most of theĮxecution time.

How Mutually Recursive Functions Are Described.

GNU gprof GNU gprof The GNU Profiler Jay Fenlason and Richard Stallman

Gprof example