X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com From: "BBelden" To: References: <000901c8852a$4cb610a0$2102a8c0 AT telecobbelden> Subject: RE: spawnl mode=P_OVERLAY Date: Thu, 13 Mar 2008 14:42:58 -0400 Message-ID: <001101c8853a$0f0ae9f0$2102a8c0@telecobbelden> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01C88518.87F949F0" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: AciFKkxRWdW+VO0iSxKmcaGH0QL+FgADnbYA In-Reply-To: <000901c8852a$4cb610a0$2102a8c0@telecobbelden> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0012_01C88518.87F949F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I have found the problem, bug?. Using cwsdpmi.exe as a TSR helped debug this. After a parent spawns(P_OVERLAY.) a child and then completely exiting all programs, djgpp did not release the (both?) processes upper memory areas. You can see this after successive calls to mem/c to see the problem. _____ From: BBelden [mailto:bbelden AT teleco DOT com] Sent: Thursday, March 13, 2008 12:50 PM To: djgpp AT delorie DOT com Subject: spawnl mode=P_OVERLAY Hello everyone. I have searched through the archives for help but didn't really help. I have multiple djgpp (32bit) compiled programs that continuously spawnl(P_OVERLAY,.) each other. The problem is, I have 100k conventional memory available at the start of these Programs. The parent always calls the child with spawnl(P_OVERLAY,.) I can do this about 6 times before crashing to dos. Can I deallocate the memory used by the parent? It seems that the parent's memory Never becomes available. Is is true that each successive call to spawnl will need ~18k of conventional memory Even if I use P_OVERLAY? Thanks for any help\ideas Bruce ------=_NextPart_000_0012_01C88518.87F949F0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I have found the problem, = bug?.

Using cwsdpmi.exe as a TSR helped = debug this.

After a parent = spawns(P_OVERLAY…) a child and then completely exiting all programs, =

djgpp did not release the (both?) processes upper memory areas.

You can see this after successive = calls to mem/c to see the problem.

 

 

 

From: = BBelden [mailto:bbelden AT teleco DOT com]
Sent: Thursday, March 13, = 2008 12:50 PM
To: djgpp AT delorie DOT com
Subject: spawnl = mode=3DP_OVERLAY

 

Hello everyone.

 

I have searched through the archives for help but didn’t really help.

 

I have multiple djgpp (32bit) compiled programs that continuously spawnl(P_OVERLAY,…) each = other.

 

The problem is, I have 100k conventional memory = available at the start of these

Programs. 

 

The parent always calls the child with spawnl(P_OVERLAY,…)

 

I can do this about 6 times before crashing to = dos.

 

Can I deallocate the memory used by the parent?  = It seems that the parent’s memory

Never becomes available. =

 

Is is true that each successive call to spawnl will = need ~18k of conventional memory

Even if I use P_OVERLAY?

 

Thanks for any = help\ideas

Bruce

 

 

------=_NextPart_000_0012_01C88518.87F949F0--