From owner-freebsd-current  Thu Jun  6 12:38:38 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA29306
          for current-outgoing; Thu, 6 Jun 1996 12:38:38 -0700 (PDT)
Received: from magigimmix.xs4all.nl (magigimmix.xs4all.nl [194.109.6.25])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA29295
          for <freebsd-current@freebsd.org>; Thu, 6 Jun 1996 12:38:33 -0700 (PDT)
Received: from asterix.xs4all.nl (asterix.xs4all.nl [194.109.6.11]) by magigimmix.xs4all.nl (8.7.5/XS4ALL) with ESMTP id VAA03257 for <freebsd-current@freebsd.org>; Thu, 6 Jun 1996 21:38:30 +0200 (MET DST)
Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id VAA07159 for freebsd-current@freebsd.org; Thu, 6 Jun 1996 21:34:46 +0200 (MET DST)
Received: (from plm@localhost) by plm.xs4all.nl (8.7.5/8.7.3) id HAA02276; Thu, 6 Jun 1996 07:33:10 +0200 (MET DST)
Date: Thu, 6 Jun 1996 07:33:10 +0200 (MET DST)
Message-Id: <199606060533.HAA02276@plm.xs4all.nl>
From: Peter Mutsaers <plm@xs4all.nl>
To: freebsd-current@freebsd.org
In-reply-to: Jake Hamby's message of Wed, 5 Jun 1996 15:40:38 -0700 (PDT)
Subject: Re: More on VM, swap leaks 
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> On Wed, 5 Jun 1996 15:40:38 -0700 (PDT), Jake Hamby
>> <jehamby@lightside.com> said:

    JH> Another possibility is a bad emacs binary.  Especially since
    JH> as part of the compilation process, emacs runs itself, loads
    JH> in a bunch of LISP, then pukes itself out as a new executable.
    JH> I shudder to think what could happen if a buggy kernel or bad
    JH> SIMM decided to rear its head at that point.

I have the same problems.

    JH> By the way, I'll be building emacs 19.31, among other things,
    JH> this week, with FreeBSD-current and Solaris/x86, so I'll post
    JH> if I have any problems with the new pmap code.  Also, I'm
    JH> using GCC 2.7.2 with 2.7.3 patches and - -O2, to try to shake
    JH> out any optimizer bugs before 2.7.3 is officially released
    JH> (and if I find none, to encourage us to put 2.7.3 in
    JH> -current!).

I built 19.31 too, with the same results. I did not yet use 2.7.2
however.