GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116

GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116

[John H. Dibbs]

HELP!!!

Porting a fairly big app from VADS ada to gnat.
Get a GNAT BUG DETECTED message, and an advisory to
call 1-800-800-4SGI. Still awaiting them to return my call.

GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116

Have recently upgraded to iris 6.2

Seems to object strongly to a for-use-at statement I'm using.
Tryed to change it to a for x'address use y, but got same error.

Thanks in advance.

Re: GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116

[John G. Volan]

Pascal Obry wrote:
> 
> "John H. Dibbs" <johnd@faac.com> wrote:
> 
> >HELP!!!
> 
> >Porting a fairly big app from VADS ada to gnat.
> >Get a GNAT BUG DETECTED message, and an advisory to
> >call 1-800-800-4SGI. Still awaiting them to return my call.
> 
> >GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116
> 
> >Have recently upgraded to iris 6.2
> 
> First of all you must upgrade to the 3.05 version of GNAT.
> 
> http://www.gnat.com/
> 
> Maybe this bug is already fixed.
> 
> Hope this help,
> Pascal.

Pascal, your advice would be sound only if John Dibbs were simply using
plain, unadorned GNAT.  However, since he quotes SGI's 1-800 number as
showing up in the Gigi abort message, I assume that he's using SGI's
port of GNAT, which I believe exploits SGI's proprietary thread library.
I haven't used this version of GNAT for several months, but the last I
heard was that SGI hasn't (officially) released anything beyond GNAT
2.07 yet, so John may be out of luck.

On the other hand, I assume that, since John's organization has a copy
of SGI's port, they must have bought it from SGI, and it would follow
that they'd have a support contract with SGI (and, by extension, with
ACT).  John, why not call up the 1-800 number and ask for help right
from the horses mouth?  :-)

------------------------------------------------------------------------
Internet.Usenet.Put_Signature 
  (Name => "John G. Volan",  Home_Email => "John_Volan@syspac.com",
   Employer => "S.A.I.C.",   Work_Email => "John_Volan@dayton.saic.com",
   Slogan => "Ada95: The World's *FIRST* International-Standard OOPL",
   Disclaimer => "My employer never defined these opinions, so using " &
     "them is totally erroneous...or is that a bounded error now? :-)");
------------------------------------------------------------------------

Re: GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116

[John G. Volan]

Apologies for replying to my own post, but I made a silly oversight:

John G. Volan wrote:
> > "John H. Dibbs" <johnd@faac.com> wrote:
[... snip ...]
> > >Get a GNAT BUG DETECTED message, and an advisory to
> > >call 1-800-800-4SGI. Still awaiting them to return my call.
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Oops, kinda bleemed over this line.

[... snip ...]
> ACT).  John, why not call up the 1-800 number and ask for help right
> from the horses mouth?  :-)

Hmm. Maybe instead you should get your manager or system administrator
to call SGI and have a word with them ... :-)

------------------------------------------------------------------------
Internet.Usenet.Put_Signature 
  (Name => "John G. Volan",  Home_Email => "John_Volan@syspac.com",
   Employer => "S.A.I.C.",   Work_Email => "John_Volan@dayton.saic.com",
   Slogan => "Ada95: The World's *FIRST* International-Standard OOPL",
   Disclaimer => "My employer never defined these opinions, so using " &
     "them is totally erroneous...or is that a bounded error now? :-)");
------------------------------------------------------------------------

Re: GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116

[Pascal Obry]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]


"John H. Dibbs" <johnd@faac.com> wrote:

>HELP!!!

>Porting a fairly big app from VADS ada to gnat.
>Get a GNAT BUG DETECTED message, and an advisory to
>call 1-800-800-4SGI. Still awaiting them to return my call.

>GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116

>Have recently upgraded to iris 6.2

First of all you must upgrade to the 3.05 version of GNAT.

http://www.gnat.com/

Maybe this bug is already fixed.

Hope this help,
Pascal.

--|------------------------------------------------------------
--| Pascal Obry                               Team-Ada Member |
--|                                                           |
--| EDF-DER-IPN-SID- Ing�nierie des Syst�mes d'Informations   |
--|                                                           |
--| Bureau G1-010           e-mail: pascal.obry@der.edfgdf.fr |
--| 1 Av G�n�ral de Gaulle  voice : +33-1-47.65.50.91         |
--| 92141 Clamart CEDEX     fax   : +33-1-47.65.50.07         |
--| FRANCE                                                    |
--|------------------------------------------------------------
--|
--|   http://ourworld.compuserve.com/homepages/pascal_obry
--|
--|   "The best way to travel is by means of imagination"

Re: GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116

[David C. Hoos, Sr.]

John G. Volan <John_Volan@syspac.com> wrote in article
<323F19D2.7A50@syspac.com>...
> Pascal Obry wrote:
> > First of all you must upgrade to the 3.05 version of GNAT.
> > 
> > http://www.gnat.com/
> > 
> > Maybe this bug is already fixed.
> > 
> > Hope this help,
> > Pascal.
> 
> Pascal, your advice would be sound only if John Dibbs were simply using
> plain, unadorned GNAT.  However, since he quotes SGI's 1-800 number as
> showing up in the Gigi abort message, I assume that he's using SGI's
> port of GNAT, which I believe exploits SGI's proprietary thread library.
> I haven't used this version of GNAT for several months, but the last I
> heard was that SGI hasn't (officially) released anything beyond GNAT
> 2.07 yet, so John may be out of luck.

You can e-mail  stebbins@engr.sgi.com (Michael Stebbins) to request a beta
tester license for gnat 3.05
-- 
David C. Hoos, Sr.,
http://www.dbhwww.com
http://www.ada95.com
> 

Re: GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116

[John H. Dibbs]

John G. Volan wrote:
> 
> Pascal Obry wrote:
> >
> > "John H. Dibbs" <johnd@faac.com> wrote:
> >
> > >HELP!!!
> >
> > >Porting a fairly big app from VADS ada to gnat.
> > >Get a GNAT BUG DETECTED message, and an advisory to
> > >call 1-800-800-4SGI. Still awaiting them to return my call.
> >
> > >GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116
> >
> > >Have recently upgraded to iris 6.2
> >
> > First of all you must upgrade to the 3.05 version of GNAT.
> >
> > http://www.gnat.com/
> >
> > Maybe this bug is already fixed.
> >
> > Hope this help,
> > Pascal.
> 
> Pascal, your advice would be sound only if John Dibbs were simply using
> plain, unadorned GNAT.  However, since he quotes SGI's 1-800 number as
> showing up in the Gigi abort message, I assume that he's using SGI's
> port of GNAT, which I believe exploits SGI's proprietary thread library.
> I haven't used this version of GNAT for several months, but the last I
> heard was that SGI hasn't (officially) released anything beyond GNAT
> 2.07 yet, so John may be out of luck.
> 
> On the other hand, I assume that, since John's organization has a copy
> of SGI's port, they must have bought it from SGI, and it would follow
> that they'd have a support contract with SGI (and, by extension, with
> ACT).  John, why not call up the 1-800 number and ask for help right
> from the horses mouth?  :-)
> 

I did talk to SGI, eventually (1 week for response).
By that time I found a work-around.

Problem encountered with a for use at.

Code notionally was:

X : float := 0;
for X use at memory_manager.next_address( X'size, "SUBSYSTEM.X" );

We use memory_manager to map things to ScramNet.
Gnat insisted that the at value had to be a prior define constant.
So changed the code to:

X_ADDRESS : constant system.address :=
    memory_manager.next_address( X'size, "SUBSYSTEM.X" );

X : float := 0;
for X use at X_ADDRESS;

This worked until in one unit I reversed the order of the first two
lines of code.

X : float := 0;
X_ADDRESS : constant system.address :=
    memory_manager.next_address( X'size, "SUBSYSTEM.X" );

for X use at X_ADDRESS;

Found what the problem was when attempted to make this change in a spec
where gnat still insisted that the at value had to be a prior defined
constant.

In a body, got the Gigi abort 116 instead. Unsure whether it was
the fact that it was in the body, or whether the new declaritive
block inside the body had anything to do with the error.

But reversing the first two lines of code got rid of the abort code.

Hope this helps someone else.

Re: GNAT V2.07 (mips-sgi-irix5.3) Gigi abort, Code=116

[John G. Volan]

John H. Dibbs wrote:
[snip] 
> I did talk to SGI, eventually (1 week for response).
> By that time I found a work-around.

Yes, after my first post, I noticed that I'd missed the fact that you'd
already put in a call to them, but that they were slow to respond.  A
whole week?  Wow, not a good sign. A few months ago, working a project
that used SGI's compiler, I recall that we got pretty good response from
them.  Then again, a week is really not all that bad, if you compare it
to the geological slowness of some Ada vendors (who shall remain
nameless) during the 1980's. :-)

Giving SGI the benefit of the doubt, maybe the 1-800 number isn't the
best avenue for getting quick help from them. You might want to look
into becoming a beta site for SGI (or get your higher-ups to look into
it).  That way, you can get interim updates of the compiler and talk
with SGI's engineers directly.  Anyway, a little bird tells me that SGI
may be coming out with an official update of their GNAT port fairly
soon.  I defer to any SGI folks who might want to chime in at this point
... 

------------------------------------------------------------------------
Internet.Usenet.Put_Signature 
  (Name => "John G. Volan",  Home_Email => "John_Volan@syspac.com",
   Employer => "S.A.I.C.",   Work_Email => "John_Volan@dayton.saic.com",
   Slogan => "Ada95: The World's *FIRST* International-Standard OOPL",
   Disclaimer => "My employer never defined these opinions, so using " &
     "them is totally erroneous...or is that a bounded error now? :-)");
------------------------------------------------------------------------