thyssen@batserver.cs.uq.oz.au (Anthony Thyssen) (10/15/90)
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?
Please follow up in this group as I am sure people would like to see/flame
the answers.
Anthony Thyssen - (Dragon Computing!) thyssen@batserver.cs.uq.oz.au
-------------------------------------------------------------------------------
"I must not fear. Fear is the mind killer. Fear is the little-death
that brings total obliteration." "Litany Against Fear" - Dune
-------------------------------------------------------------------------------waggoner@dtg.nsc.com (Mark Waggoner) (10/19/90)
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.