Date: Sun, 29 Mar 1998 14:23:18 -0800 (PST)
Message-Id: <199803292223.OAA18960@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: djgpp malloc and freeing memory on exit
Cc: Edward Cashin <edc AT arches DOT uga DOT edu>, djgpp AT delorie DOT com
Precedence: bulk

At 02:30  3/29/1998 +0300, Eli Zaretskii wrote:
>
>On Sat, 28 Mar 1998, Nate Eldredge wrote:
>
>> The only things you *need* to free yourself (AFAIK) are selectors
>> and memory allocated directly from `__dpmi' functions.
>
>Really?  Are you sure?  Can you throw together a simple test program
>which does NOT free such selectors and show that it causes a leak of
>selectors?

No, I'm not at all sure. :) That was just the only thing I didn't know for a
fact that the system frees for you, and having checked now, I can see that
it does. I guess I should have made it more clear that I didn't know what I
was talking about :).

It seemed likely to me that they needed to be explicitly freed, judging from
the trouble DJGPP's exit code goes to to free them (the 16-bit exit code and
so forth). Is that just paranoia, then?

Nate Eldredge
eldredge AT ap DOT net