From: malte@TechFak.Uni-Bielefeld.DE
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: Signal weirdness
Date: Tue, 15 Mar 1994 05:52:04 -0500 [thread overview]
Message-ID: <9403150852.AA05571@dahlie.techfak.uni-bielefeld.de> (raw)
I just tried your example on Solaris 2.3 and found a different though still
wrong behaviour:
fn sighup { echo 'caught sighup'; sleep 10 }
rc-1.5b1 + readline from bash-1.13.1
The signal gets caught but the handler is not executed until
<return> is pressed. The shell keeps running.
rc-1.5b1 without readline
Signal gets caught, the handler executed but then the shell exits
with exit code 1 and "read: Interrupted system call" message.
rc-1.4 without readline works fine.
Malte
next reply other threads:[~1994-03-15 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-03-15 10:52 malte [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-03-15 15:15 Alan Watson
1994-03-14 23:13 Tom Culliton x2278
1994-03-15 0:12 ` Vincent Broman
1994-03-14 21:46 Byron Rakitzis
1994-03-14 20:17 Tom Culliton x2278
1994-03-14 20:52 ` Chris Siebenmann
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=9403150852.AA05571@dahlie.techfak.uni-bielefeld.de \
--to=malte@techfak.uni-bielefeld.de \
--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).