Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!jade!ucbcad!ames!hao!oddjob!mimsy!cvl!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: C execution profiler
Message-ID: <6608@brl-smoke.ARPA>
Date: Thu, 29-Oct-87 23:39:35 EST
Article-I.D.: brl-smok.6608
Posted: Thu Oct 29 23:39:35 1987
Date-Received: Wed, 4-Nov-87 05:34:16 EST
References: <324@excell.colostate.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <324@excell.colostate.edu> sivagnan@excell.colostate.edu (Vasanthan S. Dasan) writes:
>Does anyone know of any C execution profiler similar to "pxp".
>What I need is a graphical representation of the flow of the
>program, and an execution history.

Generally, UNIX systems provide a "cc -p" option that will produce an
execution profile data file, which can then be displayed with the
"prof" utility.  Some versions of "prof" support graphic output,
usually standard UNIX plot(4) format, and sometimes there is a "gprof"
utility.  Check your local manual.  (By the way, the permuted index
should have found "prof" for you.)

For execution history, I usually use "ctrace".  Unfortunately
many Berkeley-based UNIXes don't supply it..