Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Authentication-Warning:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Tue, 12 Nov 2002 19:41:02 -0500 (EST)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	"Huang." <hzhr AT 21cn DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin Emacs-X uses 99% of cpu
In-Reply-To:	<3DD198B3.3020006@21cn.com>
Message-ID:	<Pine.GSO.4.44.0211121933380.4275-100000@slinky.cs.nyu.edu>
Importance:	Normal
MIME-Version:	1.0

On Wed, 13 Nov 2002, Huang. wrote:

> "J. Scott Edwards" <sedwards AT xmission DOT com> wrote:
> > [snip]
>
> Oh! I have this problem too.

For the archives:
This is an example of a completely useless message.  It doesn't add
anything at all to the discussion, and takes up list bandwidth.

Attaching the output of cygcheck would have made it marginally useful
(i.e., reporting that the problem can be reproduced on a particular
configuration).  A good contribution would have been to run emacs under
strace, for example, and provide the output (hopefully bzipped, preferably
with repeated patterns removed, ideally with some analysis attached).
Another would be to run emacs under gdb, break execution when in 100% cpu
mode, and post the stack trace.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Water molecules expand as they grow warmer" (C) Popular Science, Oct'02, p.51


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -