From owner-freebsd-current Wed Apr 14 19:38: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.25]) by hub.freebsd.org (Postfix) with ESMTP id 060AD14D15 for ; Wed, 14 Apr 1999 19:38:03 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id VAA26554; Wed, 14 Apr 1999 21:34:59 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 14 Apr 1999 21:34:59 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: green@unixhelp.org Cc: current@FreeBSD.ORG Subject: Re: swap-related problems References: <14100.62842.127882.239452@avalon.east> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14101.20360.243064.404053@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Brian Feldman on Wed, 14 April: : : ACTUALLY it would still break ANSI because the malloc itself would crash : the program, instead of touching the memory manually. The point here is that malloc can return null when it fails to allocate. I might mention that Andrew Reilly's suggestion is the winner so far, in my mind. The solution of having libc:malloc honor a 'setenv MALLOC_MMAP_STORE /path/here' would work with shrink-wrap software, and completely bypass the concerns, real and imagined, of even the most zealous advocate of overcommit purity. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message