From owner-freebsd-current  Wed Mar  1 12: 1: 8 2000
Delivered-To: freebsd-current@freebsd.org
Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130])
	by hub.freebsd.org (Postfix) with ESMTP id 47C1A37C3C8
	for <current@FreeBSD.ORG>; Wed,  1 Mar 2000 12:00:47 -0800 (PST)
	(envelope-from lyndon@orthanc.ab.ca)
Received: from orthanc.ab.ca (localhost [127.0.0.1])
	by orthanc.ab.ca (8.10.0.Beta11/8.10.0.Beta6) with ESMTP id e21K04x04001;
	Wed, 1 Mar 2000 13:00:04 -0700 (MST)
Message-Id: <200003012000.e21K04x04001@orthanc.ab.ca>
To: John Polstra <jdp@polstra.com>
Cc: current@FreeBSD.ORG
Subject: Process cleanup (was Shared memory ...)
In-reply-to: Your message of "Wed, 01 Mar 2000 11:28:13 PST."
             <200003011928.LAA75785@vashon.polstra.com> 
Date: Wed, 01 Mar 2000 13:00:04 -0700
From: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "John" == John Polstra <jdp@polstra.com> writes:

    John> Applications need to clean up after themselves.  The OS has
    John> no way of knowing whether an application wants its shared
    John> memory segments to survive after it terminates.

Tricky when the program crashes. Remember that a bug-free application
can still crash due to buggy shared-libraries.

I'm too lazy to look right this second ;-) ... do atexit() functions get
run when a process takes (say) a segmentation fault?

--lyndon


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message