paul@cernvax.UUCP (paul burkimsher) (06/09/89)
$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)