Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 17 Jan 2001 10:03:26 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: "Cygwin Mailing List (E-mail)" <cygwin AT cygwin DOT com>
Subject: Re: /usr/bin/groff:fatal error: wait: Interrupted system call
Message-ID: <20010117100326.B12915@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: "Cygwin Mailing List (E-mail)" <cygwin AT cygwin DOT com>
References: <D1F0002F0A8FD411ACEC00805FE675CE260EC2 AT zuk02exm02 DOT comm DOT mot DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <D1F0002F0A8FD411ACEC00805FE675CE260EC2@zuk02exm02.comm.mot.com>; from Ljubomir_Josifovski-BLJ01Z@email.mot.com on Tue, Jan 02, 2001 at 02:35:51PM -0000

On Tue, Jan 02, 2001 at 02:35:51PM -0000, Josifovski Ljubomir-BLJ01Z wrote:
>The man command regularly dies after brought in foreground from suspension:
>
>$ fg %3
>man objdump
>Error executing formatting or display command.
>System command (cd /usr/man ; (echo -e ".pl 1100i"; cat
>/usr/man/man1/objdump.1;
> echo ".pl \n(nlu+10") | /usr/bin/tbl | /usr/bin/groff -Tascii -mandoc |
>/bin/le
>ss) exited with status -1.
>No manual entry for objdump
>/usr/bin/groff:fatal error: wait: Interrupted system call
>Signal 1

This is a side effect of the fact that cygwin did not used to have restartable
signals.  As of the last week or so, I've started implementing this so CTRL-Z
shold work better.  There was also another unrelated problem with stopping a
cygwin process which I've also fixed.

>I wreckon the groff invoked by man is culpable. Is anyone else experiencing
>this? Solution? 
>(cygwin1.dll 1.0.7 on Win2K)
>
>Maybe connected with this (nad maybe not): ctrl-c stops working in the bash
>command window after a while - it works fine when the shell window is
>opened. Stty -a still shows ^C for intr. Any ideas?

I doubt that it is related, and I've never seen this so I can't fix it.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple