Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!tektronix!decvax!ucbvax!ucbcad!ames!hao!noao!mcdsun!dragon!charles From: charles@dragon.UUCP (Charles Wolff) Newsgroups: comp.unix.wizards Subject: Re: Tracing Stack from C Program Message-ID: <590@dragon.UUCP> Date: Fri, 30-Oct-87 11:26:12 EST Article-I.D.: dragon.590 Posted: Fri Oct 30 11:26:12 1987 Date-Received: Thu, 5-Nov-87 05:31:23 EST Reply-To: charles@dragon.UUCP (Charles Wolff, (602) 438-3432) Distribution: na Organization: Motorola Microcomputer Division, Tempe, Az. Lines: 17 In Article 4954 of comp.unix.wizards: randy@ncifcrf.UUCP (The Computer Grue) asks: > I have a question for the net: how would one go about writing a C > function that would give you a stack trace of all calls to that > function? There's a new (1986) book out called "Debugging C" by Robert Ward, published by Que Corporation, Box 50507, Indianapolis, IN 46250. Covers this topic plus a LOT of other useful tricks, caveats, etc. Good chapter on using sdb as well. Even a source listing for what they call "a full featured debugging system". $20 paperback; a good reference on debugging techniques. #include