Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!amdcad!decwrl!sqm.dec.com!jmsynge
From: jmsynge@sqm.dec.com (James M Synge, DTN 381-1545)
Newsgroups: comp.sys.amiga
Subject: Re: Question on TRAP allocation
Message-ID: <9798@decwrl.DEC.COM>
Date: Sun, 10-May-87 12:29:51 EDT
Article-I.D.: decwrl.9798
Posted: Sun May 10 12:29:51 1987
Date-Received: Sun, 10-May-87 18:59:18 EDT
Sender: daemon@decwrl.DEC.COM
Organization: Digital Equipment Corporation
Lines: 23

> 	There are two EXEC calls, AllocTrap() and FreeTrap().  The manual
> page states that they can be called "only from the currently running 
> task"...  Does this mean that each task gets its own set of traps?

	My understanding is that the trap code pointed to in your task
data structure is the code that is called to handle any trap that occurs
while your task is executing.  It is not very clear what the purpose of
AllocTrap() and FreeTrap() is.  It may be for allocating the TRAP instruction
trap values.

> 	None of the manuals state how one goes about setting a trap vector once
> one has allocated it.  Can I write directly to the vectors in low RAM?

	I think the answer is NO.  Write your trap handler and enter it in your
task structure, not in low RAM.

James Synge

USENET:  {decvax, ucbvax, allegra}!decwrl!sqm.dec.com!jmsynge
ARPAnet: jmsynge%sqm.DEC@decwrl.DEC.COM

#include <disclaimer.h>
"Ken Olsen can speak for Digital, not me!"