From owner-freebsd-hackers Thu Oct 12 19:44:16 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA10721 for hackers-outgoing; Thu, 12 Oct 1995 19:44:16 -0700 Received: from expo.x.org (expo.x.org [198.112.45.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA10716 for ; Thu, 12 Oct 1995 19:44:12 -0700 Received: from exalt.x.org by expo.x.org id AA28482; Thu, 12 Oct 95 22:43:39 -0400 Received: from localhost by exalt.x.org id WAA05209; Thu, 12 Oct 1995 22:43:38 -0400 Message-Id: <199510130243.WAA05209@exalt.x.org> To: asami@cs.berkeley.edu (Satoshi Asami) Cc: hackers@freefall.FreeBSD.org, phk@critter.tfs.com Subject: Re: xload dumps core with new phkmalloc Organization: X Consortium Date: Thu, 12 Oct 1995 22:43:37 EST From: "Kaleb S. KEITHLEY" Sender: owner-hackers@FreeBSD.org Precedence: bulk Poul-Henning sent me his malloc and xload works fine for me with MALLOC_OPTIONS=Z. I've tried everything I can think of: phkmalloc statically linked to xload; phkmalloc as malloc in libc.so.2.2; compiled -g, -O, -O2; X libs compiled -g and -O2. xload runs fine with all of them. If you're running XFree86's xload then there might be something suspect about their FreeBSD port. It's hard to guess. Dunno what else to try. It's hard to fix something you can't duplicate. :-) -- Kaleb KEITHLEY