Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!CS.BROWN.EDU!jb
From: jb@CS.BROWN.EDU
Newsgroups: comp.sys.encore
Subject: Re: EPT THREAD(disaster) - memory alloc
Message-ID: <8909111354.AA11779@snark.cs.brown.edu>
Date: 11 Sep 89 13:54:34 GMT
References: <37500008@m.cs.uiuc.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 17

The information lists how many blocks of each size are available and used.
The first block there is 8 bytes and they increase by powers of 2 from there.
The requested amount of memory in THREADgo is all the memory the process has
to use.  Stacks are allocated out of this heap as well.  Unfortunately, there
is no dynamic growth of the heap under EPT.

If the failure is actually a THREADcreate call, you might have to increase
the amount of memory you request in THREADgo.  My first guess would be that
you are failing on the third call to THREADcreate with each one having a
stack of around 4-6K.  The reason you have so much left is that it is
fragmented.  The largest block you can allocated is 512 byte.

I don't know of a good debugger for EPT.  To try and debug threads, the
debugger must understand that there is something else smaller than a
process running.

				Jim