forwarded message from Henry Cejtin

[Stephen Weeks]

Received: from maguro.epr.com ([198.3.162.27]) by exchange.epr.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id PR8RTF2R; Thu, 27 Jul 2000 10:51:12 -0700
Received: from magrathea.epr.com (firewall-user@magrathea.epr.com [198.3.160.1])
	by maguro.epr.com (8.9.3/8.9.3) with ESMTP id KAA05757
	for <sweeks@intertrust.com>; Thu, 27 Jul 2000 10:53:18 -0700 (PDT)
Received: (from uucp@localhost) by magrathea.epr.com (8.9.3/8.7.3) id KAA14706 for <sweeks@intertrust.com>; Thu, 27 Jul 2000 10:53:18 -0700 (PDT)
Received: from nodnsquery(199.249.165.245) by magrathea.epr.com via smap (V5.5)
	id xma014616; Thu, 27 Jul 00 10:52:53 -0700
Received: (from henry@localhost)
	by syzygy.clairv.com (8.9.3/8.9.3) id MAA32604
	for sweeks@intertrust.com; Thu, 27 Jul 2000 12:52:53 -0500
Message-Id: <200007271752.MAA32604@syzygy.clairv.com>
From: Henry Cejtin <henry@sourcelight.com>
To: sweeks@intertrust.com
Subject: Re: alternate stacks for signal handlers
Date: Thu, 27 Jul 2000 12:52:53 -0500

As far as I know, all the sa_restorer stuff is obsolete and I haven't ever
seen an SA_RESTORER flag.  The SA_ONSTACK is what you are supposed to use
in sigaction() to cause an alternate stack.