Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
To: cygwin@sources.redhat.com
Subject: Re: Two snapshot bugs
References: <000801c03285$ed6c49b0$21c9ca95@mow.siemens.ru>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: Kazuhiro Fujieda <fujieda@jaist.ac.jp>
Date: 10 Oct 2000 23:14:29 +0900
In-Reply-To: "Andrej Borsenkow"'s message of Tue, 10 Oct 2000 10:47:16 +0400
Message-ID: <s1ssnq47ph6.fsf@jaist.ac.jp>
Lines: 13
X-Mailer: Gnus v5.3/Emacs 19.34

>>> On Tue, 10 Oct 2000 10:47:16 +0400
>>> "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru> said:

> It is not command crashing. It is bash getting EOF sporadically and exiting.

I've experienced the same problem on recent snapshots and NT 4.0 Sp6a.
The standard input of bash seems to be sporadically closed just
after fork() or exec() is invoked. But I can't find the patter of usage
to duplicate this problem.
____
  | AIST      Kazuhiro Fujieda <fujieda@jaist.ac.jp>
  | HOKURIKU  School of Information Science
o_/ 1990      Japan Advanced Institute of Science and Technology

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com