gprof.1 (2010 09)

g
gprof(1) gprof(1)
Parents that are not profiled have the time of their profiled children propagated to them, but they appear
to be spontaneously invoked in the call graph listing, and do not have their time propagated further.
Similarly, signal catchers, even though profiled, appear to be spontaneous (although for more obscure
reasons). Any profiled children of signal catchers should have their times propagated properly unless the
signal catcher was invoked during the execution of the profiling routine, in which case all is lost.
The following limitations exist for
gprof shared library profiling on PA-RISC systems:
• Local, static, and hidden functions are not profiled.
• Shared libraries built with
-B symbolic are not profiled.
• Any function calls made from library initializers are not collected.
DEPENDENCIES
gprof cannot be used with dynamically linked executables (built with
ld -A in pre-HP-UX 10.20
releases).
AUTHOR
gprof was developed by the University of California, Berkeley.
FILES
a.out* Default object file.
gmon.out* Default dynamic call graph and profile.
gmon.sum* Summarized dynamic call graph and profile.
/usr/lib/gprof.callg*
Call graph description.
/usr/lib/gprof.flat*
Flat profile description.
/usr/lib/hpux32/libgprof.so gprof
32-bit shared library on Itanium-based systems.
/usr/lib/hpux64/libgprof.so gprof
64-bit shared library on Itanium-based systems.
/usr/lib/libgprof32.sl gprof
32-bit shared library on PA-RISC systems.
/usr/lib/pa20_64/libgprof.sl gprof
64-bit shared library on PA-RISC systems.
SEE ALSO
aCC(1), cc(1), cc_bundled(1), f90(1), ld(1), prof(1), exit(2), profil(2), sprofil(2), monitor(3C), smonitor(3C),
crt0(3).
gprof: A Call Graph Execution Profiler; Graham, S.L., Kessler, P.B., McKusick, M.K.
Proceedings of the SIGPLAN ’82 Symposium on Compiler Construction ; SIGPLAN Notices; Vol. 17, No. 6,
pp. 120-126, June 1982.
HP-UX Linker and Libraries Online User’s Guide (See the
ld +help option).
4 Hewlett-Packard Company − 4 − HP-UX 11i Version 3: September 2010