X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10112110529.AA23541@clio.rice.edu>
Subject: Re: go32-v2 memory chompage [was: Re: v2.03 refresh ...]
To: djgpp-workers AT delorie DOT com
Date: Mon, 10 Dec 2001 23:29:28 -0600 (CST)
Cc: eliz AT is DOT elta DOT co DOT il, acottrel AT ihug DOT com DOT au
In-Reply-To: <10112102224.AA25539@clio.rice.edu> from "Charles Sandmann" at Dec 10, 2001 04:24:58 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Okay, simple tests, all from the command line (after a exe2coff djecho.exe
on each appropriate directory):

1) v2.03: go32-v2 djecho hi
   No memory lossage.  (So it's in something we changed).
2) v2.03 update: go32-v2 djecho hi
   About 35K lost per call (two TBs plus extras)
   Note: kill ntvdm frees it all up!
3) current cvs: go32-v2 djecho hi
   About 35K lost per call (not a refresh issue, just a new bug)
4) v2.03, patched djecho executable to do different get/set psp:
   No memory lossage

So, the Andrew's problem is not specific to v2.03 refresh.  cvs either calls
go32-v2 less frequently, or there were partial build results, or more
resources or something.  The bug is there in cvs too.

Good news is that the alternate "restore psp" code does not seem to cause
these problems (so I think I have a fix).  I'll put it in cvs and in a
refresh.