Date: Tue, 6 Apr 1999 09:26:45 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Michael Bukin <bukinm AT inp DOT nsk DOT su>
cc: djgpp AT delorie DOT com
Subject: Re: What's Broken in Windows DPMI
In-Reply-To: <20emly7gdn.fsf@Sky.inp.nsk.su>
Message-ID: <Pine.SUN.3.91.990406092618.6187H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 6 Apr 1999, Michael Bukin wrote:

> When DOS stub executes int 0x21, ah=0x4B (load and execute), DOS
> allocates some memory with int 0x21, ah=0x48.

Sorry, I don't understand.  Which ``DOS stub'' are you referring to
here?  If that's the DJGPP stub (stub.asm), then AFAIK it doesn't call
Int 21h/AH=4Bh when it runs on Windows.

> So, even if we can fix
> problem with leaking selectors by reusing deallocated selectors,
> problem with leaking DOS memory will remain (while we did not find
> workaround).

How much memory does the allocation request?  If it's not much, you
might not notice it.

> I have tested spawn on Borland C 3.1.  When it calls "load and
> execute" interrupt, there are no calls to "allocate memory"
> interrupt.  Now I'm trying to compare spawn functions in DJGPP and
> Borland C.

As far as I could see, there are no calls in DJGPP's spawn to any
functions that allocate DOS memory directly.