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.1 required=5.0 tests=BAYES_00, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,7e8cebf09cf80560 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 Path: g2news1.google.com!news1.google.com!goblin1!goblin3!goblin.stu.neva.ru!exi-transit.telstra.net!news.telstra.net!exi-spool.telstra.net!exi-reader.telstra.net!not-for-mail From: "robin" Newsgroups: comp.lang.ada References: Subject: Re: How would Ariane 5 have behaved if overflow checking were notturned off? Date: Wed, 16 Mar 2011 21:41:10 +1100 X-Newsreader: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Message-ID: <4d80b140$0$43832$c30e37c6@exi-reader.telstra.net> NNTP-Posting-Host: 123.3.18.145 X-Trace: 1300279617 exi-reader.telstra.net 43832 123.3.18.145:1028 Xref: g2news1.google.com comp.lang.ada:18241 Date: 2011-03-16T21:41:10+11:00 List-Id: Vinzent Hoefler <0439279208b62c95f1880bf0f8776eeb@t-domaingrabbing.de> wrote in message ... >Elias Salomão Helou Neto wrote: >> Since then I have been wondering. If compiler checking where actually >> turned on, what would have happened? >The same, according to the specification. >> How could it avoid the disaster? >Not at all. On the contrary., an error handler would have performed something useful. The crux of the matter is that the data bus would not have been loaded with an error number [which was then treated as guidance data]. >> Right now I think of three possibilities, the two former seem very >> unlikely to me. > >> a) It would, even if the problem went undetected during testing, have >> made the developers actually develop code handling this exceptional >> possibility. >By handling it exactly the way it was supposed to be: >Assuming a hardware error and leave control to the redundant subsystem. That was the major blunder that they made, namely, treating a programming error as a hardware error. By doing that, they guaranteed failure of the mission. >> Which one, if any, is close to reality? >As it has been mentioned here many times before, the software behaved >exactly as specified and it is very unlikely that _any_ error handling >could have avoided the problem An error handler would have rescued the mission.