Re: Is malloc()ed storage freed upon program termination?

Article View: comp.std.c

Article #4072

#4072

From: Jim Hennessy
Date: Wed, 20 Sep 1995 19:57

14 lines
1348 bytes

Christopher R. Volpe (volpe@bart.crd.ge.com) wrote:

: It's an OS issue.

I'm not sure I agree that it's an OS issue.  Shouldn't the standard define
my responsibilities as a programmer if I want to write a portable program?
I understand that most OS complications are beyond the scope of the C
standard, but I think perhaps something should have been said about this
matter.  For example, the standard says that open streams are closed on
program termination (AFTER it says that unwritten data is flushed).  Why was
it necessary to say that?  Even in this thread, there is not general
agreement whether it's safe to end the program without freeing storage.  I
agree that doing so is certainly the defensive way to program, but I was
wondering if there was a guarantee in the standard that I missed.  It seems not.

Technical Details

Message-ID: <43prn7$h0@homer.alpha.net>

Path: arc1-ca.pugleaf.net!homer.alpha.net!earth!jimh

References: <43l16d$3dp@homer.alpha.net> <811549923.10778@contech.demon.co.uk> <43pdon$b3i@rdsunx.crd.ge.com>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!homer.alpha.net!earth!jimh
From: jimh@earth.execpc.com (Jim Hennessy)
Newsgroups: comp.std.c
Subject: Re: Is malloc()ed storage freed upon program termination?
Date: 20 Sep 1995 19:57:27 GMT
Organization: Exec-PC -- (800)-EXECPC-1
Distribution: world
Message-ID: <43prn7$h0@homer.alpha.net>
References: <43l16d$3dp@homer.alpha.net> <811549923.10778@contech.demon.co.uk> <43pdon$b3i@rdsunx.crd.ge.com>
Reply-To: jph@vnet.ibm.com
NNTP-Posting-Host: earth.execpc.com
X-Newsreader: TIN [version 1.2 PL2]

Reply to Parent Message