From: Jason Tyler <jason@itntl.bhp.com.au>
To: rc@hawkwind.utcs.toronto.edu
Cc: j@nc.itntl.bhp.com.au
Subject: rc-1.5b2 and SIGQUIT
Date: Tue, 30 Sep 1997 01:21:43 -0400 [thread overview]
Message-ID: <199709300521.PAA23897@nc.itntl.bhp.com.au> (raw)
On many platforms (at least Solaris, Linux, and OSF3.2), rc-1.5b2 dies
if it receives a SIGQUIT whilst inside rc_read(). Adding the following
code (which was removed sometime between 1.4 and 1.5b2) back into
fdgchar() fixes this:
*** input.c.old Tue Sep 30 14:27:28 1997
--- input.c Tue Sep 30 15:07:15 1997
***************
*** 140,145 ****
--- 140,147 ----
long /*ssize_t*/ r = rc_read(istack->fd, inbuf + 2, BUFSIZE);
sigchk();
if (r < 0) {
+ if (errno == EINTR)
+ continue;
uerror("read");
rc_exit(1);
}
However, this may be bad; was the EINTR check taken out for a good
reason? If so, how else can I fix the problem?
j
next reply other threads:[~1997-09-30 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-30 5:21 Jason Tyler [this message]
1997-09-30 19:44 ` Scott Schwartz
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=199709300521.PAA23897@nc.itntl.bhp.com.au \
--to=jason@itntl.bhp.com.au \
--cc=j@nc.itntl.bhp.com.au \
--cc=rc@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).