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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,4590cbe206fc9bb9
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.224.111.8 with SMTP id q8mr2090945qap.3.1346969612241;
        Thu, 06 Sep 2012 15:13:32 -0700 (PDT)
Received: by 10.52.34.115 with SMTP id y19mr741062vdi.1.1346969612200; Thu, 06
 Sep 2012 15:13:32 -0700 (PDT)
Path: 
 da15ni851qab.0!nntp.google.com!b19no1305218qas.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 6 Sep 2012 15:13:32 -0700 (PDT)
In-Reply-To: <87bohi26kl.fsf@ludovic-brenta.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=74.69.172.183;
 posting-account=YkFdLgoAAADpWnfCBA6ZXMWTz2zHNd0j
NNTP-Posting-Host: 74.69.172.183
References: <6dfcb108-01de-42e4-962a-87a9ac91741c@googlegroups.com>
 <87fw6u2abw.fsf@ludovic-brenta.org>
 <016ff78a-64f9-4a42-a079-e544526e2f8a@googlegroups.com>
 <87bohi26kl.fsf@ludovic-brenta.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <0b591914-1915-4c8b-b0d5-ebf188fc2de4@googlegroups.com>
Subject: Re: Stumped: Seg Fault with System.Secondary_Stack.SS_Mark()
From: awdorrin <awdorrin@gmail.com>
Injection-Date: Thu, 06 Sep 2012 22:13:32 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Date: 2012-09-06T15:13:32-07:00
List-Id: <comp.lang.ada>

Ah that is interesting. How did you know that was using the secondary stack=
?

My system is a Intel based Dell pc running Debian Linux. I think it has 8gb=
 RAM (at home now will have to double check tomorrow.) So i shouldn't be ru=
nning out of memory, although I would not be surprised if this code contain=
s memory leaks that could be effecting the stack.=20

I spent most of today trying to track this secondary stack issue down.=20

Thanks!