From owner-freebsd-hackers  Thu Oct 12 20:02:24 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id UAA11326
          for hackers-outgoing; Thu, 12 Oct 1995 20:02:24 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA11314
          for <hackers@freefall.FreeBSD.org>; Thu, 12 Oct 1995 20:02:21 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id UAA02437; Thu, 12 Oct 1995 20:02:13 -0700
Date: Thu, 12 Oct 1995 20:02:13 -0700
Message-Id: <199510130302.UAA02437@silvia.HIP.Berkeley.EDU>
To: kaleb@x.org
CC: hackers@freefall.FreeBSD.org, phk@critter.tfs.com
In-reply-to: <199510130243.WAA05209@exalt.x.org> (kaleb@x.org)
Subject: Re: xload dumps core with new phkmalloc
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-hackers@FreeBSD.org
Precedence: bulk

 * Poul-Henning sent me his malloc and xload works fine for me with 
 * MALLOC_OPTIONS=Z.

That means it's not fine. :)

MALLOC_OPTIONS=Z means malloc acts like calloc.  X libs shouldn't
depend on that.

Satoshi