From owner-freebsd-current  Wed Mar 26 00:47:44 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA26472
          for current-outgoing; Wed, 26 Mar 1997 00:47:44 -0800 (PST)
Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA26459
          for <current@freebsd.org>; Wed, 26 Mar 1997 00:47:39 -0800 (PST)
Received: (from bsdcur@localhost)
          by shadows.aeon.net (8.8.5/8.8.3) id IAA11159;
          Wed, 26 Mar 1997 08:47:31 GMT
From: mika ruohotie <bsdcur@shadows.aeon.net>
Message-Id: <199703260847.IAA11159@shadows.aeon.net>
Subject: Re: SIGTERMs killing X
In-Reply-To: <199703260521.WAA27235@phaeton.artisoft.com> from Terry Lambert at "Mar 25, 97 10:21:01 pm"
To: terry@lambert.org (Terry Lambert)
Date: Wed, 26 Mar 1997 10:47:31 +0200 (EET)
Cc: current@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> are the cause of a memory leak.  You should consider using an X
> server that has been linked against Poul-Henning Kamp's new malloc,
> which is capable of sbrk'ing back to the system.

do i get phk_malloc when i compile whole X from the /usr/ports collection?


mickey