public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Josifovski Ljubomir-BLJ01Z <Ljubomir_Josifovski-BLJ01Z@email.mot.com>
To: "Cygwin Mailing List (E-mail)" <cygwin@sourceware.cygnus.com>
Subject: /usr/bin/groff:fatal error: wait: Interrupted system call
Date: Tue, 02 Jan 2001 06:36:00 -0000	[thread overview]
Message-ID: <D1F0002F0A8FD411ACEC00805FE675CE260EC2@zuk02exm02.comm.mot.com> (raw)

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

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?

thanks,

-- 
Ljubomir Josifovski
mailto:L.Josifovski@dcs.shef.ac.uk,blj01z@email.mot.com
http://www.dcs.shef.ac.uk/~ljupco


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

             reply	other threads:[~2001-01-02  6:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-02  6:36 Josifovski Ljubomir-BLJ01Z [this message]
2001-01-17  7:03 ` Christopher Faylor
2001-01-27  7:49   ` Christopher Faylor
2001-01-02  7:49 Josifovski Ljubomir-BLJ01Z

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D1F0002F0A8FD411ACEC00805FE675CE260EC2@zuk02exm02.comm.mot.com \
    --to=ljubomir_josifovski-blj01z@email.mot.com \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).