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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,c9d5fc258548b22a
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news1.google.com!postnews.google.com!s28g2000prb.googlegroups.com!not-for-mail
From: "Nasser M. Abbasi" <nma@12000.org>
Newsgroups: comp.lang.ada
Subject: Re: How do I write directly to a memory address?
Date: Tue, 8 Feb 2011 02:15:09 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <4bb6cd17-561e-4bb4-95a5-e7ab78d22673@s28g2000prb.googlegroups.com>
References: 
 <67063a5b-f588-45ea-bf22-ca4ba0196ee6@l11g2000yqb.googlegroups.com>
 <iimmvm$tsp$1@news.eternal-september.org> <8r86vgFc3uU1@mid.individual.net>
 <iimrem$udn$1@news.eternal-september.org>
 <19fh1chm74f9.11cws0j5bckze.dlg@40tude.net>
 <fa33fca1-c95b-4558-8a4c-7b3276366ffc@m13g2000yqb.googlegroups.com>
 <4d4ff70e$0$6886$9b4e6d93@newsspool2.arcor-online.net>
 <737a6396-72bd-4a1e-8895-7d50f287960e@d28g2000yqc.googlegroups.com>
 <4d5008a5$0$6879$9b4e6d93@newsspool2.arcor-online.net>
 <eda00084-fcc3-416c-bd3e-8b9e9c1a4b40@o13g2000yql.googlegroups.com>
 <4d5031fe$0$6765$9b4e6d93@newsspool3.arcor-online.net>
 <1f229967-d3cf-42b6-8087-c97ee08652f3@i40g2000yqh.googlegroups.com>
 <4d5110ea$0$7669$9b4e6d93@newsspool1.arcor-online.net>
 <1fb3ce45-ffcc-4c1c-8f76-d151975c8425@x1g2000yqb.googlegroups.com>
 <4d511500$0$7665$9b4e6d93@newsspool1.arcor-online.net>
NNTP-Posting-Host: 24.7.153.92
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1297160109 31331 127.0.0.1 (8 Feb 2011 10:15:09
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 8 Feb 2011 10:15:09 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: s28g2000prb.googlegroups.com; posting-host=24.7.153.92;
 posting-account=YqIC9AoAAADap7NvyM7RBldP6UMj5cTQ
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13)
 Gecko/20101203 Firefox/3.6.8 NET_mmhpset,gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:16975
Date: 2011-02-08T02:15:09-08:00
List-Id: <comp.lang.ada>

On Feb 8, 2:03=A0am, Georg Bauhaus <rm-host.bauh...@maps.futureapps.de>
wrote:
> On 2/8/11 10:58 AM, Ludovic Brenta wrote:
>
> >> (c) by single case logic, Ada's type system has not prevented
> >> deaths in Ariane 5 anyway.
>
> > Huh?
>
> You don't even know this?

Hello;

>From wiki:

http://en.wikipedia.org/wiki/Ariane_5_Flight_501

"Because of the different flight path, a data conversion from a 64-bit
floating point to 16-bit signed integer value caused a hardware
exception (more specifically, an arithmetic overflow, as the floating
point number had a value too large to be represented by a 16-bit
signed integer). Efficiency considerations had led to the disabling of
the software handler (in Ada code) for this error trap"

So, the problem was "disabling of the software handler".

So, it seems to me that Ada worked as expected? It DID detect the
overflow.

But someone has disabled run-time exception handler.

--Nasser