Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ucla-cs!zen!ucbvax!jade!saturn!skinner
From: skinner@saturn.ucsc.edu (Robert Skinner)
Newsgroups: comp.unix.wizards
Subject: Re: Looking for a C call-graph generator ...
Message-ID: <566@saturn.ucsc.edu>
Date: Thu, 23-Jul-87 02:44:23 EDT
Article-I.D.: saturn.566
Posted: Thu Jul 23 02:44:23 1987
Date-Received: Sat, 25-Jul-87 12:38:29 EDT
References: <8230@brl-adm.ARPA>
Organization: U.C. Santa Cruz, CIS/CE.
Lines: 46
Summary: info, not sarcasm

In article <8230@brl-adm.ARPA>, franco@MIKEY.BBN.COM (Frank A. Lonigro) writes:
> Wayne:
> 	Try 'cflow : generate C flow graph' or 'ctags : create a tags file'
> or 'ctrace : C program debugger' or 'trace : trace system calls of programs'.
> If this doesn't help, I would suggest to you to take volume 1 of your systems
> manual and flip through page by page and learn a few new commands.
> 
> -franco

great,

someone asks about the existence of a tool that I could use also, and
we get the above response.  OK, Frank, I've 'learned a few new commands'
and here's what I know:

	cflow:	not present on either 4.3 or SYSV system I use

	ctags:  sure, it shows you where routines are defined, and I
		use it for `vi`, but it doesn't show who calls who
		(it does help narrow down the search by hand)

	ctrace:	not present

	trace:	not present

	cxref:	tried it on our SYSV system.  It barfed when I tried to
		do 'complicated' things like:
			
			#define	A  5
			#define B  A
		
		and it claims that its errors are cryptic but usually mean that
		the file wouldn't compile anyway, sure.


I also remember that there was a pretty good program also called 'cxref'
that we picked up at my last job.  I had the impression it was public
domain or came from Usenix.  It had only minor bugs, and I used it 
successfully on a 17K line program.

back to the original question:  what works?

Robert Skinner
skinner@saturn.ucsc.edu