Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!mintaka!olivea!apple!voder!dtg.nsc.com!waggoner
From: waggoner@dtg.nsc.com (Mark Waggoner)
Newsgroups: comp.sys.amiga.tech
Subject: Re: tc_MemEntry in the Task Structure?
Message-ID: <1461@icebox.nsc.com>
Date: 19 Oct 90 16:41:01 GMT
References: <5231@uqcspe.cs.uq.oz.au>
Reply-To: waggoner@icebox.UUCP (Mark Waggoner)
Organization: National Semiconductor, Santa Clara
Lines: 21

In article <5231@uqcspe.cs.uq.oz.au> thyssen@batserver.cs.uq.oz.au writes:
>What is the tc_MemEntry in the Task structure for? Is it used? Can I
>make use of it? How? Does Lattice or Manx use it?
>

I'm not sure what the system puts on the tc_MemEntry list, but I know
that if you add MemEntry's on to it, they will be freed when the task
is terminated.  

Some time ago, I looked at some C startup code that automatically
detached the process and ran it in the background.  It converted the
process' seglist to a MemList and then tacked it on to the end of the
MemEntry list so that the code would be freed upon exit.  I don't know
if Manx or Lattice use this method in their startup code of the same
type.


-- 
Mark Waggoner  Santa Clara, CA    (408) 721-6306         waggoner@dtg.nsc.com 
 Unofficially representing National Semiconductor Local Area Networks Group
                   Officially misrepresenting myself.