From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 00:09:40 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 6731B37B401 for ; Thu, 24 Jul 2003 00:09:40 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-67-119-53-152.dsl.lsan03.pacbell.net [67.119.53.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 947E343FD7 for ; Thu, 24 Jul 2003 00:09:39 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id ECADD66D32; Thu, 24 Jul 2003 00:09:36 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id CC054C12; Thu, 24 Jul 2003 00:09:36 -0700 (PDT) Date: Thu, 24 Jul 2003 00:09:36 -0700 From: Kris Kennaway To: Mike Tancsa Message-ID: <20030724070936.GA16762@rot13.obsecurity.org> References: <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> User-Agent: Mutt/1.4.1i cc: Gabor cc: freebsd-stable@freebsd.org cc: Kris Kennaway 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 07:09:40 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 23, 2003 at 11:44:11PM -0400, Mike Tancsa wrote: > At 08:15 PM 7/23/2003 -0700, Kris Kennaway wrote: > >On Wed, Jul 23, 2003 at 01:34:27PM -0400, Gabor wrote: > > > >> Here is the tail end of the output. It dies when trying to poke at > >> the memory using memset. If I just malloc without the memset, it > >> never even dies. > > > >Ah, the annual "memory overcommit" thread. I thought we were overdue > >for one. >=20 >=20 > But why does the man page for malloc (3) say, >=20 > If malloc() fails, a NULL pointer is returned. Words fail me. Kris --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/H4YwWry0BWjoQKURAprjAJwJSPTpVGWuQ/ogsKX5pcxhGd3rMACfTji2 XzkCbfFRSeaUr49gbieOasw= =tW8v -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62--