From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,a7209bea6d326945,start
X-Google-Attributes: gid103376,public
From: SamuelFigueroa@no_spam.usa.net (Samuel Figueroa)
Subject: Interrupt handlers and exceptions
Date: 1998/06/12
Message-ID: <6lrurs$4fm$1@news2.apple.com>#1/1
X-Deja-AN: 362110660
Organization: Apple Computer, Inc.
Newsgroups: comp.lang.ada
Date: 1998-06-12T00:00:00+00:00
List-Id: <comp.lang.ada>


Paragraph 7 of Section C.3 of the ARM says that exceptions cannot be  
propagated from interrupt handlers.  Does this mean that an interrupt  
handler cannot raise something like Constraint_Error, and expect a task's  
exception handler to be invoked?  Is there any way for an interrupt  
handler to cause a task's exception handler to be invoked, or to somehow  
cause the termination of the task that was executing when the interrupt  
occurred?  (For the purposes of this discussion, one could envision an  
interrupt handler for page faults, in which one might want to raise some  
exception, and either have the program's exception handler take some  
action, or terminate the program itself.)

- Sam Figueroa (figueroa.nospam@cs.nyu.edu)