Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site dartvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!petrus!bellcore!decvax!dartvax!andyb
From: andyb@dartvax.UUCP (Andy Behrens)
Newsgroups: net.unix-wizards
Subject: Problems with alarm (Xenix 3.2e)
Message-ID: <3727@dartvax.UUCP>
Date: Wed, 23-Oct-85 16:35:16 EDT
Article-I.D.: dartvax.3727
Posted: Wed Oct 23 16:35:16 1985
Date-Received: Fri, 25-Oct-85 04:07:31 EDT
Reply-To: andyb@dartvax.UUCP (Andy Behrens)
Distribution: net
Organization: Dartmouth College, Hanover, NH
Lines: 32

Does anybody know why...

On XENIX 3.2e, the sleep routine calls signal, passing the routine to
execute on an alarm call, then calls alarm.  The routine to execute
mysteriously executes the following 286 code before returning:

	push di
	push si
	pop  si
	pop  di

Why?  I can't get timer traps to work.  Must I do something mysterious
like this?  I am getting segmentation violations on the Altos 2086.  I
am calling signal( SIGALRM, xxx ), where xxx is set to routine(), and
routine is:

	int routine() {
		flag = TRUE;
	}

P.S.  This works MOST of the time, but sometime produces a segmentation
violation.

P.P.S. I would dearly love to find someone who can answer such questions.  
Dealing with ALTOS is impossible!

					Andy Behrens

{astrovax,decvax,cornell,ihnp4,linus}!dartvax!andyb.UUCP
andyb@dartmouth.CSNET
andyb%dartmouth@csnet-relay.ARPA
RFD 1 Box 116, Union Village, Vt. 05043