Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!steinmetz!dawn!stpeters
From: stpeters@dawn.steinmetz (Dick St.Peters)
Newsgroups: comp.unix.wizards
Subject: Re: Stack trace from inside a program . . .
Message-ID: <7741@steinmetz.steinmetz.UUCP>
Date: Sat, 31-Oct-87 16:37:55 EST
Article-I.D.: steinmet.7741
Posted: Sat Oct 31 16:37:55 1987
Date-Received: Thu, 5-Nov-87 03:19:10 EST
References: <151@ncifcrf.UUCP>
Sender: root@steinmetz.steinmetz.UUCP
Reply-To: dawn!stpeters@steinmetz.UUCP (Dick St.Peters)
Organization: General Electric CRD, Schenectady, NY
Lines: 15
Keywords: dbx 'where' C innards

In article <151@ncifcrf.UUCP> randy@ncifcrf.UUCP (The Computer Grue) writes:
>    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?

I did this once under VMS.  The experience strongly suggests such a
function would be machine-, system-, and even compiler-dependent.
(It was different for the two C compiler I had.)

True in general?
--
Dick St.Peters                        
GE Corporate R&D, Schenectady, NY
stpeters@ge-crd.arpa              
uunet!steinmetz!stpeters