From owner-freebsd-standards@FreeBSD.ORG  Tue Mar  2 15:50:17 2004
Return-Path: <owner-freebsd-standards@FreeBSD.ORG>
Delivered-To: freebsd-standards@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id F04FD16A4CE
	for <freebsd-standards@FreeBSD.ORG>;
	Tue,  2 Mar 2004 15:50:17 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1F45043D49
	for <freebsd-standards@FreeBSD.ORG>;
	Tue,  2 Mar 2004 15:50:17 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i22NoAu9089172;
	Wed, 3 Mar 2004 00:50:10 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Stefan Farfeleder <stefan@fafoe.narf.at>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Tue, 02 Mar 2004 23:39:54 +0100."
             <20040302223950.GF1021@wombat.fafoe.narf.at> 
Date: Wed, 03 Mar 2004 00:50:10 +0100
Message-ID: <89171.1078271410@critter.freebsd.dk>
cc: freebsd-standards@FreeBSD.ORG
Subject: Re: standards/62858: malloc(0) not C99 compliant 
X-BeenThere: freebsd-standards@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Standards compliance <freebsd-standards.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-standards>,
	<mailto:freebsd-standards-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-standards>
List-Post: <mailto:freebsd-standards@freebsd.org>
List-Help: <mailto:freebsd-standards-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-standards>,
	<mailto:freebsd-standards-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2004 23:50:18 -0000

In message <20040302223950.GF1021@wombat.fafoe.narf.at>, Stefan Farfeleder writes:
>On Mon, Mar 01, 2004 at 05:37:31PM +0100, Poul-Henning Kamp wrote:
>
>> I want to make sure people who malloc(0) and then deref the pointer get
>> the core dump they need to debug their problem.
>
>So you want malloc(0) to return a different pointer to unmapped memory
>every time it is called?

Yes.

>> Does the code also fail if you give
>> malloc the 'V' flag ?
>
>No, modulo PR bin/62859 where I forgot to CC you :)

I'll look at this tomorrow if I have time.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.