From owner-cvs-all Fri Nov 12 9:29:58 1999 Delivered-To: cvs-all@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 9D41314CC8; Fri, 12 Nov 1999 09:29:44 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id D6C711C6D; Sat, 13 Nov 1999 01:29:41 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Fumerola Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/stdlib malloc.3 In-reply-to: Your message of "Fri, 12 Nov 1999 11:04:57 EST." Date: Sat, 13 Nov 1999 01:29:41 +0800 From: Peter Wemm Message-Id: <19991112172941.D6C711C6D@overcee.netplex.com.au> Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Bill Fumerola wrote: > On Fri, 12 Nov 1999, Peter Wemm wrote: > > > Log: > > Go to a bit more trouble to make it absolutely clear that malloc(3) > > does not zero the allocated memory. > > Unlike OpenBSD, which does. Ewww. Not according to what I see on their cvsweb for malloc.[c3]. They zero calloc() (as do we), but not malloc(). They recently had a change to have calloc() not also zero the result from malloc() if malloc was already in zero mode, but it isn't by default according to the source.. Now, if they set the malloc options some other way by default then that's silly. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message