Xref: utzoo comp.unix.questions:27861 comp.unix.internals:1750 comp.unix.programmer:803
Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!spool2.mu.edu!uunet!mcsun!ukc!newcastle.ac.uk!turing!nknrc
From: K.N.R.Conner@newcastle.ac.uk (Kevin Conner)
Newsgroups: comp.unix.questions,comp.unix.internals,comp.unix.programmer
Subject: Undocumented Sigvec Call?
Message-ID: <1991Jan3.104509.17119@newcastle.ac.uk>
Date: 3 Jan 91 10:45:09 GMT
Sender: news@newcastle.ac.uk
Organization: Computing Laboratory, U of Newcastle upon Tyne, UK NE1 7RU.
Lines: 22

Hiya, I posted this to the net just before christmas and got no replies,
so here I go again.

I am developing a checkpoint utility on an encore multimax machine and came
across a problem which manifested itself during a profile run.

Sigvec is used to send information about a sigentry procedure to the kernel.
It uses signal 1024 (0x400) to send this information although it does return
-1.

My questions are :-
	Is this documented somewhere?
	If so, where?
	Are there any more of these lying about for any more system calls?

Thanks
	Kev

"I didn't say this!  I wasn't here!"

K.N.R.Conner@uk.ac.newcastle          K.N.R.Conner@newcastle.ac.uk
...!ukc!newcastle.ac.uk!K.N.R.Conner