From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10206151815.AA23136@clio.rice.edu>
Subject: Re: unixy sbrk and win2k
To: eliz AT is DOT elta DOT co DOT il
Date: Sat, 15 Jun 2002 13:15:27 -0500 (CDT)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <8296-Sat15Jun2002210528+0300-eliz@is.elta.co.il> from "Eli Zaretskii" at Jun 15, 2002 09:05:28 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> > But I wouldn't expect EMACS to be calling sbrk() when CTRL is being
> > pressed?  
> 
> Why not?  Emacs is a memory-intensive program: Lisp objects are
> constantly being born and once in a while deleted by the garbage
> collector.  It's quite possible that CTRL is being pressed while
> Emacs called sbrk, isn't it?

I wouldn't be expecting Emacs to be doing anything unless I was giving
it instructions to do something, and I wouldn't expect pressing Ctrl
to be an instruction to do something.  If it was doing something I would
expect it to be using and freeing memory, not constantly growing that
memory such that a call to sbrk() was required.

Thus, I don't understand Emacs; to fix it someone who has an idea what
it's doing needs to write a small test program which shows the same
symptoms.