Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!<UNAUTHENTICATED>+
From: Richard.Draves@CS.CMU.EDU
Newsgroups: comp.os.mach
Subject: Re: Stack space for threads
Message-ID: <8ZXlVY600hYP12M48r@cs.cmu.edu>
Date: 20 Dec 89 05:28:04 GMT
References: <688@augean.OZ>
Sender: rpd@M.GP.CS.CMU.EDU
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 14
In-Reply-To: <688@augean.OZ>

Excerpts from netnews.comp.os.mach: 14-Dec-89 Stack space for threads
Ian Dall@augean.OZ (1032)

How is automatic variable space handled for threads?

The Mach kernel doesn't have any policy for allocating stacks.  The guy
who initializes a thread should allocate a stack and set the thread's
stack register appropriately.

The C-Threads library gives a new thread a fixed-size region of
zero-fill memory for its stack.  It doesn't provide a fork primitive for
threads.

Rich