www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/03/25/07:32:46

Date: Wed, 25 Mar 1998 13:31:05 +0100 (MET)
From: Olivier Perron <perron AT art DOT alcatel DOT fr>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp AT delorie DOT com
Subject: Re: flex never frees some buffers !?
In-Reply-To: <Pine.SUN.3.91.980325151535.28802D-100000@is>
Message-Id: <Pine.GSO.3.96.980325132049.22281B-100000@rtbsci143s>
Mime-Version: 1.0

On Wed, 25 Mar 1998, Eli Zaretskii wrote:

> 
> On Tue, 24 Mar 1998, Olivier Perron wrote:
> 
> > When the program that use flex exits, it leaves ~16 kbytes of allocated
> > memory which is never freed.
> > On unix it is not a problem because when a process die any unfreed memory
> > that was allocated by the process will be freed by the kernel.
> > But on DOS machines, this unfreed memory still remain as allocated and is
> > definitivly lost until next reboot.
> 
> Please describe how did you get to the conclusion that on DOS the memory 
> is not freed.  As far as I know, all the memory, both conventional and 
> extended, *is* freed when the DJGPP program exits.
> 
I'm very sorry, but I just simply thought that on DOS the allocated memory
was not freed. Don't ask me wy ! I just thought it was so.
Again, sorry for the inconvenience.

Just to know, so that I can't do any mistakes any more: is this behaviour
typical to DJGPP programs + CWSDPMI or is it a normal behaviour for any
programs (not only DJGPP ones) and with any DPMI providers (like Windows).

Olivier.


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019