cvs.gedasymbols.org/archives/browse.cgi | search |
Date: | Wed, 29 Dec 1999 10:12:46 +0200 (IST) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | Chaos <chengin AT alpha DOT net DOT pl> |
cc: | djgpp AT delorie DOT com |
Subject: | Re: freeing memory and exiting (safely) |
In-Reply-To: | <848onr$rvo$3@portraits.wsisiz.edu.pl> |
Message-ID: | <Pine.SUN.3.91.991229100951.11728H-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Sun, 26 Dec 1999, Chaos wrote: > >Just terminate with 'exit(1);', and that's it. > > Hmm. I read that exit(X) DOES NOT do anything to memory. In info (as well as > in Borland 3.1 help) there is that exit() sends exit code to OS, closes any > stream and finaly terminates program. And what about memory? All the memory is deallocated, and the related selectors freed, as part of the DJGPP exit code. See the file src/libc/crt0/crt0.S in the library sources, for the gory details.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |