Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site wateng.UUCP Path: utzoo!watmath!wateng!ksbszabo From: ksbszabo@wateng.UUCP (Kevin S. B. Szabo) Newsgroups: net.sources Subject: Re: Bug in calls and everybody who wonders what CALLS does. Message-ID: <1090@wateng.UUCP> Date: Tue, 12-Jun-84 21:37:03 EDT Article-I.D.: wateng.1090 Posted: Tue Jun 12 21:37:03 1984 Date-Received: Wed, 13-Jun-84 02:38:23 EDT Organization: U of Waterloo, Ontario Lines: 49 I have had a number of requests for more information on calls(1), here is a portion of the manual page. If I get enough requests I will repost it. CALLS(1) UNIX Programmer's Manual CALLS(1) NAME calls - print out calling pattern of functions in a program DESCRIPTION calls accepts from standard input a file which should be the source of a programme, and outputs the analysed calling pat- tern to standard output. It is intended to help analyse the flow of a programme by laying out the functions called in the manner used in "Software Tools". For example: main abc a << abc << b def d >> e [external] in which main calls abc and def, abc calls a and b which are defined within the same source file, and def calls d (defined in the same source) and e, which is presumably a library programme or defined in a different source file. The function a calls abc in a recursive loop. FUNCTION LIST Function names within the input programme may be selected as roots of the layout (default "main" in C). For example, using the previous programme: calls def abc> e [external] abc a << abc << b AUTHOR M.M.Taylor (DCIEM) Modified for V7 and stdio, Alexis Kwan (HCR for DCIEM) -- Kevin Szabo watmath!wateng!ksbszabo (Elec Eng, U of Waterloo)