From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 19:34:37 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDF1837B401 for ; Wed, 23 Jul 2003 19:34:37 -0700 (PDT) Received: from altair.mukappabeta.net (p3E9BE28C.dip.t-dialin.net [62.155.226.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ABBD43FAF for ; Wed, 23 Jul 2003 19:34:36 -0700 (PDT) (envelope-from mkb@mukappabeta.de) Received: from mukappabeta.de (localhost [127.0.0.1]) by altair.mukappabeta.net (Postfix) with ESMTP id 4FAE35959 for ; Thu, 24 Jul 2003 04:38:58 +0200 (CEST) Message-ID: <3F1F46C2.5000106@mukappabeta.de> Date: Thu, 24 Jul 2003 04:38:58 +0200 From: Matthias Buelow Organization: GeFoekoM e.V. User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4a) Gecko/20030504 X-Accept-Language: de-de, de, en-gb, en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030723221336.GA26555@pit.databus.com> <20030723223654.GA24008@moghedien.mukappabeta.net> <20030723224436.GD22166@Odin.AC.HMC.Edu> <20030724021726.GJ430@gsmx07.alcatel.com.au> In-Reply-To: <20030724021726.GJ430@gsmx07.alcatel.com.au> X-Enigmail-Version: 0.75.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 02:34:38 -0000 Peter Jeremy wrote: > FreeBSD behaviour in the face of swap shortage is a regular and > popular discussion topic. I suggest that a perusal of the archives Yes but I for example have had this issue since 2.1-R (when I started using it), freezing when the system trashes, without hope for resolve, or other short-on-memory related ailments. The fact that it's still on-topic in mailing lists after many years shows that the issue hasn't really been resolved yet. You'll see postings like the above in 5 or even 10 years still if a proper solution won't be found and implemented until then. -- Matthias Buelow; mkb@{mukappabeta.de,informatik.uni-wuerzburg.de}