Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!mit-eddie!uw-beaver!zephyr.ens.tek.com!tektronix!reed!vishnu!celarier
From: celarier@vishnu.reed.edu (Stuart Celarier)
Newsgroups: comp.lang.c
Subject: Re: C program hierarchical listing
Message-ID: <15856@reed.UUCP>
Date: 9 Jan 91 21:58:25 GMT
References: <1991Jan8.191524.14403@nas.nasa.gov>
Sender: news@reed.UUCP
Lines: 18
To: dueker@xenon.arc.nasa.gov

Let me recommend that you investigate gprof, the
call graph profiler on UNIX systems (well, most of
them).  This produces a lengthy report, based not on
the source code but on the actual execution(s) of the
program, which will tell you for each function:  how
many times it was called (and how long it took), the
names of all _executed_ parents and children, along 
with appropriate counts.  Very valuable for speed 
optimization.

I used this utility extensively when I inherited a
large software package from a third party, and was able
to discover a great amount of information about the
program structure and interaction in a short amount of
time.

-Stuart Celarier
<celarier@reed.bitnet>