Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!decwrl!pa.dec.com!decuac!e2big.mko.dec.com!francus
From: francus@e2big.mko.dec.com (Yoseff Francus)
Newsgroups: comp.unix.wizards
Subject: Re: What is sigcleanup?
Message-ID: <1991Jan28.220801.21109@e2big.mko.dec.com>
Date: 28 Jan 91 22:08:01 GMT
References: <1991Jan22.153802.9869@daimi.aau.dk> <119782@uunet.UU.NET>
Reply-To: francus@e2big.mko.dec.com (Yoseff Francus)
Organization: Digital Equipment Corporation
Lines: 19

In article <119782@uunet.UU.NET> rbj@uunet.UU.NET (Root Boy Jim) writes:
>In article <1991Jan22.153802.9869@daimi.aau.dk> kaja@daimi.aau.dk (Kaja P. Christiansen) writes:
>>What is "sigcleanup" doing?
>

sigcleanup is called after the user written signal handler is finished.
A chmk $139 is done. This puts you into syscall(...) In syscall
there is an explicit check for 139 and a call to sigcleanup.
It resets the kernel stack so that you eventually return
to the point in you program where you made the system call which later
checked for pending signale which then dod the signal trampoline stuff
and so on. The above is completely true for a VAX, your mileage will
vary on other architectures.


-- 
In Xanadu did Kubla Khan
A stately pleasure dome decree
But only if the NFL 
To a franchise would agree

francus%metsny.mko.dec.com@decwrl.dec.com