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,WEIRD_PORT
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,e44790cdcea9da82
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: "Martin Dowie" <martin.dowie@baesystems.com>
Newsgroups: comp.lang.ada
Subject: Re: Problem with -gnatt
Date: Fri, 8 Oct 2004 10:43:45 +0100
Organization: BAE SYSTEMS
Message-ID: <41665fe4$1_1@baen1673807.greenlnk.net>
References: <41651D37.4030805@mailinator.com> <c0a9d.3371$4b.445@trndny09>
 <2skt9qF1ljjdtU1@uni-berlin.de> <4165472D.2030704@mailinator.com>
 <416573FA.4010003@mailinator.com> <87k6u2mj08.fsf@insalien.org>
 <4166538E.6090907@mailinator.com>
X-Trace: news.uni-berlin.de gsR2awqQkzcPkR+vi2+ETAQXlBcytEIXKmWmd7xA64400FvuVu
X-Orig-Path: baen1673807.greenlnk.net!baen1673807!not-for-mail
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Original-NNTP-Posting-Host: baen1673807.greenlnk.net
Xref: g2news1.google.com comp.lang.ada:4917
Date: 2004-10-08T10:43:45+01:00
List-Id: <comp.lang.ada>

Alex R. Mosteo wrote:
> I don't think so. It bails out in a storage error in the instance of
> one of the new AI.302 containers which I'm using in place of Charles. See:
>
> +===========================GNAT BUG
> DETECTED==============================+
>> 3.15p  (20020523) (i686-pc-linux-gnu) Storage_Error stack overflow
>> (or erroneous memory access)| Error detected at
>> ../../containers/a-cohama.adb:508:4
> [../download/adagio-download-slot.ads:78:4]|
>
> Should I report the bug? I'm not customer of ACT so I don't have
> customer number, for example.
>
> Maybe the use of the Ada.Containers is a practice of risk? ;)

I'm guessing that "adagio-download-slot.ads:78" is a new instance of the
hash map container? Is it also nested within a package spec? If so, try
moving it to be at library level and with it back into the original, parent
package...

Cheers

-- Martin