From owner-freebsd-current  Wed Oct  9 21:53:02 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA14454
          for current-outgoing; Wed, 9 Oct 1996 21:53:02 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA14447;
          Wed, 9 Oct 1996 21:52:52 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id XAA08260; Wed, 9 Oct 1996 23:46:11 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199610100446.XAA08260@dyson.iquest.net>
Subject: Re: 'dead' binary stays 'dead'?
To: msmith@atrad.adelaide.edu.au (Michael Smith)
Date: Wed, 9 Oct 1996 23:46:11 -0500 (EST)
Cc: dyson@FreeBSD.org, msmith@atrad.adelaide.edu.au, current@FreeBSD.org
In-Reply-To: <199610100435.OAA17545@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 10, 96 02:05:39 pm
Reply-To: dyson@FreeBSD.org
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Argh.  Not what I wanted to know 8(
> 
I do get bad news once in a while also.  Note that it CAN be hardware,
but could be an errant driver, VM system, anywhere in the kernel.
>
> > We all need to keep an eye on the problem...  This is the first time that
> > I have heard of it -- but doesn't mean that it isn't there :-)...
> 
> Would it be possible to have the memory reclaimed immediately if the program
> is killed by an unhandled signal?  Generally speaking one wouldn't expect
> that would be a situation one would optimise for, and it would perhaps
> improve robustness in cases such as this...
> 
That is actually an interesting idea!!!

John