From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 04:13:21 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 21B2A37B401 for ; Sat, 26 Jul 2003 04:13:21 -0700 (PDT) Received: from mailhost.firstcallgroup.co.uk (dilbert.firstcallgroup.co.uk [194.200.93.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AD6543F85 for ; Sat, 26 Jul 2003 04:13:20 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by mailhost.firstcallgroup.co.uk with local (Exim 4.12) id 19gMzE-000Nau-00; Sat, 26 Jul 2003 12:13:16 +0100 To: dalroi@solfertje.student.utwente.nl, freebsd-stable@freebsd.org In-Reply-To: <20030725221644.21516376@solfertje.student.utwente.nl> Message-Id: From: Pete French Date: Sat, 26 Jul 2003 12:13:16 +0100 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: Sat, 26 Jul 2003 11:13:21 -0000 > That probably would mean that all the software should switch to a new > way of allocating memory, but it's a start... ...its only "a start" if you consider the current behaviour to be a problem. which under most normal uses of FreeBSd (and all the other UNIXs which do this) it doesnt seem to be. I realise its a bit of a shock to realise whats going on, but its not something most people run into in practice. -pcf.