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: <10112110844.AA25323@clio.rice.edu>
Subject: Re: go32-v2 memory chompage [was: Re: v2.03 refresh ...]
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Tue, 11 Dec 2001 02:44:33 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com, acottrel AT ihug DOT com DOT au
In-Reply-To: <Pine.SUN.3.91.1011211101133.19E-100000@is> from "Eli Zaretskii" at Dec 11, 2001 10:12:30 AM
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

> Ah, but invoking a program via go32-v2 is not really nesting, as far
> as the DPMI host and NTVDM are concerned, right?  

Correct.

> To them, this looks like a single crazy DOS program which just likes 
> to longjmp and lcall too much.
> 
> So perhaps the cleanup code which tries to fix NTVDM should detect
> this situation and do nothing.

I don't see how a child program could know if it was run from 
go32-v2 (and if it wasn't trivial to do this, if we would want to
try and put this in a refresh).

> > I wrote the original versions of all that stuff so I remember :-)
> 
> I think the original version didn't allocate all those additional DOS
> buffers.  Perhaps I'm mistaken.

The original tried to re-use the go32-v2 transfer buffer and stub and
PSP.  But this wasn't good for debugging.  When debugging was fixed...

Well, it's almost 3am here so I should try to get some sleep.  I'll let
you reflect on psp's from stubinfo, go32-v2, and alternate nesting
fixes.

(If there is a way in dosexec to make it call go32-v2 less frequently,
should we consider that?)