Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Date:	Fri, 04 Jun 2004 09:32:53 -0700
From:	Edwin Goei <Edwin DOT Goei AT Sun DOT COM>
Subject:	Fork, xemacs 21.4.13, and shell-mode
To:	cygwin AT cygwin DOT com
Message-id:	<40C0A435.2020301@sun.com>
MIME-version:	1.0
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

Hi,

I use shell-mode in xemacs with cygwin.  This works great on a unix 
system, but with the cygwin version, xemacs sometimes goes crazy and 
takes 100% of the CPU and I often have to kill xemacs.  I think it's 
related to shell-mode because sometimes when I kill a shell-mode window, 
the CPU usage goes back to normal.

This just happened to me again and when I try to exec another process 
from xemacs itself, I get the following error:

Doing fork: Resource temporarily unavailable

However, in my other shell-mode buffer where I'm running bash, I can 
fork a new process such as run "ls".

Anyone else see this or have suggestions on how to debug it?

-Edwin

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -