From: Tom Culliton <culliton@clark.net>
To: rc@hawkwind.utcs.toronto.edu
Subject: rc, signals, readline, and Linux
Date: Wed, 5 Mar 1997 00:55:45 -0500 [thread overview]
Message-ID: <199703050555.AAA13494@explorer2.clark.net> (raw)
8-) 8-) 8-) Anybody who has been paying attention will know that I've
been fighting a battle with the combination mentioned above. Both rc
and readline like to play with signals, readline always acts like a
slow system call when the signal hanlder returns, and leaves things
FUBAR'ed if it doesn't. 8-) 8-) 8-)
So my big **** eating grin might tell you something. 8-) Thats right,
unless I've overlooked something really dumb, it's fixed!!! This fix
probably applies to anyone using readline, especially on Posix type
systems. Basically it entails ALWAYS treating readline as a slow
system call, retrying the read on EINTR, and doing some deep secret
readline magic in the rc signal catcher. I'll try to post a context
diff against virgin rc-1.5betadev-1 as soon as I make a few posix-isms
conditional.
Tom (one very tired and happy hacker)
next reply other threads:[~1997-03-05 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-05 5:55 Tom Culliton [this message]
1997-03-09 4:24 ` Stephen Tell
1997-03-09 5:31 Tom Culliton
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=199703050555.AAA13494@explorer2.clark.net \
--to=culliton@clark.net \
--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).