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.223.84 with SMTP id ij20mr3114133qab.5.1347040244022; Fri, 07 Sep 2012 10:50:44 -0700 (PDT) Received: by 10.236.74.38 with SMTP id w26mr978471yhd.18.1347040243996; Fri, 07 Sep 2012 10:50:43 -0700 (PDT) Path: da15ni12456543qab.0!nntp.google.com!b19no4151223qas.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 7 Sep 2012 10:50:43 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=192.31.106.36; posting-account=YkFdLgoAAADpWnfCBA6ZXMWTz2zHNd0j NNTP-Posting-Host: 192.31.106.36 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> <0b591914-1915-4c8b-b0d5-ebf188fc2de4@googlegroups.com> <00367705-1c58-4ae1-9965-c6415feae8c3@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Stumped: Seg Fault with System.Secondary_Stack.SS_Mark() From: awdorrin Injection-Date: Fri, 07 Sep 2012 17:50:44 +0000 Content-Type: text/plain; charset=ISO-8859-1 Date: 2012-09-07T10:50:43-07:00 List-Id: On Friday, September 7, 2012 1:07:36 PM UTC-4, Simon Wright wrote: > > That's what I was thinking (when I came across this problem, the Ada > code was a callback from a VxWorks task, so not the same scenario > exactly). The code that I am working on migrating to Linux came from a VxWorks system, so it may be a more similar scenario than you thought. ;-) The code compiled and ran with those changes. I haven't seen any Seg Faults yet. However now I appear to have another issue likely related to trying to run at RT priorities. Thanks once again, to both of you, for the help! Hopefully I'll get this next priority issue worked out and will be able to verify that this did resolve the secondary stack issues.