Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!ogccse!blake!uw-beaver!cornell!rochester!rit!tropix!ur-valhalla!uhura.cc.rochester.edu!sunybcs!boulder!ncar!ames!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: SVR4
Message-ID: <10563@smoke.BRL.MIL>
Date: 15 Aug 89 16:40:09 GMT
References: <10506@smoke.BRL.MIL> <14020066@hpisod2.HP.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 15

In article <14020066@hpisod2.HP.COM> decot@hpisod2.HP.COM (Dave Decot) writes:
>> AT&T presented an overview of SVR4 at a BOF session at the Baltimore USENIX.
>I found a reference in a draft of SVID89 to a function called
>getcontext(BA_OS), but no entry in the book for it.
>Will such a function exist, and if so, what will it do?

My notes from the BOF session say that getcontext() gets current user
context (ucontext structure), which is described as being similar to
BSD sigcontext: signal mask, machine context, current stack.  As near
as I can tell from the copy of the VuGraph, this is in addition to
the additional siginfo structure that will be fed to three-argument
signal handlers when SA_SIGINFO is enabled in the sigaction flag.
Apparently you have to make the specific system call getcontext() to
retrieve the ucontext information.  There is also a setcontext() for
the reverse.  The notes did not include detailed interface information.