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:	<10112102244.AA14310@clio.rice.edu>
Subject:	Re: v2.03 refresh ready for review/testing
To:	acottrel AT ihug DOT com DOT au (Andrew Cottrell)
Date:	Mon, 10 Dec 2001 16:44:37 -0600 (CST)
Cc:	eliz AT is DOT elta DOT co DOT il (Eli Zaretskii), djgpp-workers AT delorie DOT com
In-Reply-To:	<009201c181c0$d703a9d0$0102a8c0@acceleron> from "Andrew Cottrell" at Dec 11, 2001 08:18:57 AM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
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

> I tried 2 configurations:-
> 1) I tried the go32-v2.exe from the updatd 2.03 zip files and it failed in
> the same spot. mem /c & mem /d looked the same.
> 2) I tried the 2.04 go32-v2.exe and it failed in the same spot. I did a CVS
> update and build on XP as I was building the updated 2.03 on the 98 box.

Okay ... either it always does this under CVS and we've missed it or 
something outside go32-v2 fixes it?  Or avoids go32-v2?

> There should be no exe's with unixy sbrk set.

Okay, I think we figure out where the blocks are coming from.

> Just a note about the psp issue that in CVS dosexec.c has a call to
> __maybe_fix_w2k_ntvdm_bug(void)  which relates to a psp issue. The call is
> not in the updated 2.03 sources.

Correct.  It is a "were're really paranoid" call.  The set psp after the 
return from an exec is there to catch if our program aborts so badly we 
don't pass through _exit.  The process of exiting with a "zero" psp is
what nukes NTVDM.  I don't think this is an issue here (you built some
tests with it with no changes, right?)  Our PSP might be incorrect for
a longer window but we don't do anything which could kill NTVDM then.

- Raw text -