Date: Fri, 13 Oct 1995 07:03:31 EST From: "Kaleb S. KEITHLEY" <kaleb@x.org> To: hackers@freefall.FreeBSD.org Cc: asami@cs.berkeley.edu, phk@critter.tfs.com Subject: Re: xload dumps core with new phkmalloc Message-ID: <199510131103.HAA05408@exalt.x.org> In-Reply-To: Your message of Fri, 13 Oct 1995 10:14:59 EST. <1260.813575699@critter.tfs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Poul-Henning sent me his malloc and xload works fine for me with >> MALLOC_OPTIONS=Z. To which Poul-Henning said: >You need to set MALLOC_OPTIONS=J, 'Z' means zero the allocation, >'J' means 'junk'. And Satoshi said: >That means it's not fine. :) >MALLOC_OPTIONS=Z means malloc acts like calloc. X libs shouldn't >depend on that. Yeah, well, forgive me for not spelling everything out in nauseous detail; after spending hours building and rebuilding libraries (and finding nothing wrong) I wasn't feeling particularly loquacious. I tried Z, J, and nothing; xload works fine for me using phkmalloc. X libraries do *not* depend on the memory being zeroed. -- Kaleb KEITHLEY
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510131103.HAA05408>