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-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,5e0cbbafd9d00923
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-03-13 10:28:06 PST
Path: 
 supernews.google.com!sn-xit-03!supernews.com!logbridge.uoregon.edu!hammer.uoregon.edu!skates!not-for-mail
From: Stephen Leake <stephen.a.leake.1@gsfc.nasa.gov>
Newsgroups: comp.lang.ada
Subject: Re: EXCEPTION_ACCESS_VIOLATION and others stories
Date: 13 Mar 2001 13:15:49 -0500
Organization: NASA Goddard Space Flight Center
Message-ID: <uy9u9sffu.fsf@gsfc.nasa.gov>
References: <lB9r6.38$Tv1.323767@nnrp2.proxad.net>
NNTP-Posting-Host: anarres.gsfc.nasa.gov
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: skates.gsfc.nasa.gov 984508195 16612 128.183.220.71 (13 Mar 2001
 18:29:55 GMT)
X-Complaints-To: dscoggin@cne-odin.gsfc.nasa.gov
NNTP-Posting-Date: 13 Mar 2001 18:29:55 GMT
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.6
Xref: supernews.google.com comp.lang.ada:5689
Date: 2001-03-13T18:29:55+00:00
List-Id: <comp.lang.ada>

"Etienne Baudin" <etienne.baudin@wanadoo.fr> writes:

> EXCEPTION_ACCESS_VIOLATION
>     Appears when I compile with
> <<gnatmake -gnatpn -O2 -mpentium -funroll-loops -fomit-frame-pointer %1
> -largs -s e:\gllib\opengl32.lib e:\gllib\glu32.lib e:\gllib\libglut32.a>>
> 
> with
> <<gnatmake %1
> -largs -s e:\gllib\opengl32.lib e:\gllib\glu32.lib e:\gllib\libglut32.a>>
> there isn't problem

-fomit-frame-pointer is probably dangerous with GNAT; why are you
 specifying it?

> else : is "tab(1..3):=anothertab(1..3)" faster than
> tab(1):=anothertab(1) tab(2):=anothertab(2) tab(3):=anothertab(3) or
> is it the same execution time ?

Time it on your machine and your compiler and your set of options; no
other way to know.

> Then, does anyone know this compilar message and could tell me what
> is wrong ? <<access-to-variable designates constant>>

It means you have an object of an access-to-variable type that you are
trying to make point to a constant (probably an "in" parameter). This
is illegal, because later code could then try to change the constant
by assigning via the access object. If it is an "in" parameter, change
it to either an "in out" parameter or an "access" parameter, or
redefine the subprogram called to take an access-to-constant type.

-- 
-- Stephe