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: 101deb,12d7915e86ce849c X-Google-Attributes: gid101deb,public X-Google-Thread: 103376,5f645669103080a8 X-Google-Attributes: gid103376,public X-Google-Thread: 12b42c,12d7915e86ce849c X-Google-Attributes: gid12b42c,public From: clodius@hotspec.lanl.gov (William Clodius) Subject: Re: Ariane Crash (Was: Adriane crash) Date: 1996/07/31 Message-ID: #1/1 X-Deja-AN: 172258272 sender: clodius@hotspec.lanl.gov references: <4tkfe5$did@goanna.cs.rmit.edu.au> <4tnip9$k0s@zeus.orl.mmc.com> 12: 15:37 GMT organization: Los Alamos National Laboratory newsgroups: comp.lang.ada,comp.lang.pl1,rmit.cs.100 Date: 1996-07-31T00:00:00+00:00 List-Id: One point I would like to emphasize is that the out of bounds error occured in a portion of the software that was not useful once launch commenced. This has several implications 1. Utilization of this software should have ceased as soon after launch as possible, freeing computational resources as soon as possible. 2. The effect of exception handling on processor utilization for this portion of the software should have been important only during the prelaunch phase, when I suspect processor utilization would have been minimal. 3. The proper action to take in the event of an exception in this portion of the software should be based on what the proper action should be before launch. I would not be surprised to discover that the proper action would be to shut down the processor at that stage. -- William B. Clodius Phone: (505)-665-9370 Los Alamos National Laboratory Email: wclodius@lanl.gov Los Alamos, NM 87545