From owner-cvs-all Fri Nov 12 10:35:43 1999 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 06C6215505; Fri, 12 Nov 1999 10:35:25 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA06609; Fri, 12 Nov 1999 19:34:39 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Bill Fumerola , Peter Wemm , 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:12:40 MST." <199911121812.LAA17860@harmony.village.org> Date: Fri, 12 Nov 1999 19:34:39 +0100 Message-ID: <6607.942431679@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk In message <199911121812.LAA17860@harmony.village.org>, Warner Losh writes: >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. I can imagine two reactions, neither of which would appear sane to me. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message