From: culliton@srg.srg.af.mil (Tom Culliton x2278)
To: rc@hawkwind.utcs.toronto.edu
Subject: Signal weirdness
Date: Mon, 14 Mar 1994 15:17:05 -0500 [thread overview]
Message-ID: <9403141517.aa11662@ceres.srg.af.mil> (raw)
I just got a nasty suprise with signal handlers. While trying to test:
fn sigwinch {eval `{/usr/bin/X11/resize}}
I discovered that rc (1.5beta1 with GNU readline linked in, under SunOs
(4.1.3) and SCO-ODT (1.1 and 3.0)) dies after running the handler for a
signal that isn't ignored. For example setting the following:
fn sighup {echo 'got sighup';sleep 10}
and then sending the shell a sighup (kill -1 11532) from another window
causes it to print the message, wait, and the shell to exit. If the
signal handler ends with a return command you get an error message but
the shell doesn't die.
This is really ugly, anyone have a clue? I'd test this without readline
and even dig through code if work wasn't so piled up on my desk. Maybe
in a week or so. In the mean time, can anyone else verify this?
Tom
next reply other threads:[~1994-03-14 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-03-14 20:17 Tom Culliton x2278 [this message]
1994-03-14 20:52 ` Chris Siebenmann
1994-03-14 21:46 Byron Rakitzis
1994-03-14 23:13 Tom Culliton x2278
1994-03-15 0:12 ` Vincent Broman
1994-03-15 10:52 malte
1994-03-15 15:15 Alan Watson
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=9403141517.aa11662@ceres.srg.af.mil \
--to=culliton@srg.srg.af.mil \
--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).