Date: Tue, 31 Mar 1998 21:55:33 -0800 (PST)
Message-Id: <199804010555.VAA22806@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: sandmann AT clio DOT rice DOT edu (Charles Sandmann),
        eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: djgpp malloc and freeing memory on exit
Cc: edc AT arches DOT uga DOT edu, djgpp AT delorie DOT com
Precedence: bulk

At 08:52  3/30/1998 -0600, Charles Sandmann wrote:

>2) Some dpmi providers do not free selectors when nesting.  DJGPP has 
>   special code to try and free as many as it can on exiting.  It cannot
>   free them all (it's current CS/SS for example).

This might be totally wrong, but from my reading of the exit code, it sure
tries. It looks like it writes some 16-bit code to its transfer buffer whose
job is to free the last selectors and memory block. Since this runs in real
mode, it shouldn't need any selectors of its own. Am I missing something?

Do I understand correctly that, barring a bug in the DPMI server, selectors
and such will be freed when the *parent* exits?

Nate Eldredge
eldredge AT ap DOT net