From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 2 19:19:42 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11FF016A4CF for ; Tue, 2 Mar 2004 19:19:42 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A21D843D3F for ; Tue, 2 Mar 2004 19:19:41 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i233IVDL017403 for ; Tue, 2 Mar 2004 22:18:31 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i233IVB8017400 for ; Tue, 2 Mar 2004 22:18:31 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 2 Mar 2004 22:18:31 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: hackers@FreeBSD.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Looking for static analysis tool to generate call graphs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2004 03:19:42 -0000 On Mon, 1 Mar 2004, Robert Watson wrote: > I'd like to generate static call graphs from sections of src/sys/kern, > src/sys/net, and src/sys/netinet, and ideally, get an output that looks > pretty when printed to a (perhaps large) piece of paper. It doesn't > need to be able to handle function pointer magic in structures (vnode > operations, socket operations, file descriptor operations, sysinits, > etc); I just want a fairly high-level graph to get a feel for particular > chunks of code spanning a couple of C files. Anyone have any > recommendations? Preferably something that can actually parse the > variant of C we use in our kernel :-). Well, using a scary combination of grep, awk, a long list of "omit this" regexp's, and prcc from cflow, I got the following: http://www.watson.org/~robert/freebsd/20040302-sockets.ps Duck and cover. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research