Date:	Mon, 13 Aug 2001 12:46:47 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<6480-Mon13Aug2001124647+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC:	pavenis AT lanet DOT lv, djgpp-workers AT delorie DOT com
In-reply-to:	<10108100454.AA13597@clio.rice.edu> (sandmann@clio.rice.edu)
Subject:	Re: Selector Exhaustion
References:	<10108100454 DOT AA13597 AT clio DOT rice DOT edu>
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

> From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> Date: Thu, 9 Aug 2001 23:54:24 -0500 (CDT)
> 
> Dosexec selectors=27f:2af
> gcc ... -c d0200.S
> Dosexec selectors=27f:2af
> Load error: no DOS memory
> Dosexec selectors=27f:2af
> make.exe[2]: *** [d0200.o] Error 1
> Dosexec selectors=227:257
> make.exe[1]: *** [all_subs] Error 2
> Dosexec selectors=1cf:1ff
> make.exe: *** [all] Error 2
> 
> So, my problem with selectors went away with the above patch, but now I
> die due to no DOS memory :-P (it does run longer).  Now what is strange
> is before I added the diagnostic print I think I still leaked, but I
> can't be 100% sure my make build was correct.  So, does NTVDM leak dos memory
> too?

You could (a) remove the printf and see if it still leaks DOS memory;
and (b) add another printf that prints the amount of free DOS memory.
You could even (c) run some utility which reports DOS memory blocks
used up by programs after spawn returns.  The results might tell
something interesting.

- Raw text -