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=0.7 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no
	version=3.4.4
Xref: utzoo comp.lang.ada:2399 comp.os.vms:15133
Path: utzoo!attcan!uunet!mcvax!cernvax!paul
From: paul@cernvax.UUCP (paul burkimsher)
Newsgroups: comp.lang.ada,comp.os.vms
Subject: $forcex to a Vax-Ada tasking program ignored. Why?
Message-ID: <1013@cernvax.UUCP>
Date: 9 Jun 89 15:50:43 GMT
Reply-To: paul@cernvax.UUCP (paul burkimsher)
Followup-To: comp.lang.ada
Organization: CERN European Laboratory for Particle Physics, CH-1211 Geneva, Switzerland
List-Id: <comp.lang.ada>

$forcex to a Vax-Ada tasking program ignored. Why? 

I call $FORCEX and give it the pid of another process that is running a
Vax-Ada tasking program. 3 times out of 4 it works no problem. The target
program exits. 

About 1 in 4 times when I $FORCEX, one of the Ada tasks catches an
"exception" in a WHEN OTHERS. That task executes the WHEN OTHERS and
completes, but then the rest of the system still chugs merrily along (...as
it should given that the "exception" was only "seen" by one task...) 

But why is the Ada exception handler getting control? I don't want my Ada
handler to get control! I'm trying to kill off the whole lot. I would like
it to close all files for me though, so STOP/ID is not really an
alternative. 

Worse, last time I knew (which was probably under V4.7) it all worked fine.
I've only just noticed the problem now I'm testing the program after making
some other changes. 

We run VMS V5.0-2 on a Lavc. 
Ada is VAX Ada V1.5-44 

Any hints, clues, recipes, explanations etc, gratefully received.

Paul Burkimsher
paul@online.decnet.cern.ch
vxcern::paul (HEPNET)
paul%online@cernvax (BITNET)
paul%cern.online@uk.ac.ean-relay (Janet)
...!cernvax!paul (UUCP)