From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from relay1.UU.NET ([192.48.96.5]) by hawkwind.utcs.toronto.edu with SMTP id <24169>; Mon, 14 Mar 1994 15:40:31 -0500
Received: from uucp3.uu.net (via uucp3-le1.UU.NET) by relay1.UU.NET with SMTP 
	(5.61/UUNET-internet-primary) id AAwhfu12975; Mon, 14 Mar 94 15:40:10 -0500
Received: from srg.UUCP by uucp3.uu.net with UUCP/RMAIL
        ; Mon, 14 Mar 1994 15:40:10 -0500
Received: from ceres.srg.af.mil by srg.srg.af.mil
	id aa01443; Mon, 14 Mar 94 15:16:17 EST
From:	culliton@srg.srg.af.mil (Tom Culliton x2278)
X-Mailer: SCO System V Mail (version 3.2)
To:	rc@hawkwind.utcs.toronto.edu
Subject: Signal weirdness
Date:	Mon, 14 Mar 1994 15:17:05 -0500
Message-Id: <9403141517.aa11662@ceres.srg.af.mil>

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