From owner-cvs-all Fri Nov 12 10:12:59 1999 Delivered-To: cvs-all@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7552614A1C; Fri, 12 Nov 1999 10:12:31 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA05051; Fri, 12 Nov 1999 11:12:19 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA17860; Fri, 12 Nov 1999 11:12:40 -0700 (MST) Message-Id: <199911121812.LAA17860@harmony.village.org> To: Bill Fumerola Subject: Re: cvs commit: src/lib/libc/stdlib malloc.3 Cc: Peter Wemm , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org In-reply-to: Your message of "Fri, 12 Nov 1999 11:04:57 EST." References: Date: Fri, 12 Nov 1999 11:12:40 -0700 From: Warner Losh Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk In message Bill Fumerola writes: : > 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. Checking the code, it appears that you can force it to do so, but the same is true of FreeBSD. I can just imagine Theo's reaction to someone trying to commit the a change which would make malloc always bzero the buffer returned. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message