From: "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: What's Broken in Windows DPMI
Date: Mon,  5 Apr 1999 16:29:34
Organization: Aspen Technology, Inc.
Lines: 9
Message-ID: <3708e4ee.sandmann@clio.rice.edu>
References: <20vhfc47t7 DOT fsf AT Sky DOT inp DOT nsk DOT su>
NNTP-Posting-Host: dmcap2.aco.aspentech.com
X-NewsEditor: ED-1.5.8
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> Anybody know what exactly is the problem with leaking descriptors on
> Windows-9X?  

If you have a nested application (DPMI app #1, like GCC, calls DPMI app
#2, like CC1) windows should clean up the selectors it allocated for the
child application on it's exit.  The child can't clean them up, since it
must have a protected mode CS/SS to call the DPMI exit call.  This is the
bug - Windows does NOT clean up things on nested DPMI calls - and leaks
4 selectors per nesting.