Xref: utzoo comp.unix.questions:30343 comp.unix.internals:2536 comp.unix.programmer:1563 comp.lang.c:38217 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!sun-barr!olivea!tymix!cirrusl!ss168!dhesi From: dhesi%cirrusl@oliveb.ATC.olivetti.com (Rahul Dhesi) Newsgroups: comp.unix.questions,comp.unix.internals,comp.unix.programmer,comp.lang.c Subject: Re: Unix Stack Frame Questions Message-ID: <3051@cirrusl.UUCP> Date: 12 Apr 91 01:46:23 GMT References: <125@epic.epic.com> <3465@unisoft.UUCP> <19157@rpp386.cactus.org> <3035@cirrusl.UUCP> Sender: news@cirrusl.UUCP Distribution: na Organization: Cirrus Logic Inc. Lines: 17 In kers@hplb.hpl.hp.com (Chris Dollin) writes: >Does calling it a stack frame make it a stack frame? It might be just a record >in the heap. Whether we call that a ``stack frame'' or not seems to be a matter >of taste. A stack frame can be in the heap. (Some of the other posters would then call it an activation record. But it quacks like a stack frame, so I call it one.) By the way, a stack can be in the heap too! In fact in many environments a process can allocate memory in the heap, then create a new process whose runtime stack is in that allocated memory. -- Rahul Dhesi UUCP: oliveb!cirrusl!dhesi