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-Thread: 103376,fea50f781bb229dc X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!feeder2.cambriumusenet.nl!feed.tweaknews.nl!87.79.20.105.MISMATCH!news.netcologne.de!ramfeed1.netcologne.de!newsfeed.freenet.ag!newsfeed.kamp.net!newsfeed.kamp.net!nx02.iad01.newshosting.com!209.197.12.242.MISMATCH!nx01.iad01.newshosting.com!newshosting.com!69.16.185.16.MISMATCH!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post02.iad.highwinds-media.com!news.flashnewsgroups.com-b7.4zTQh5tI3A!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: Symbolic tracebacks on Debian References: <85f51aeb-cac9-4591-921a-a7f50c8ef142@a21g2000yqn.googlegroups.com> <1pup1z7a4f1pq$.of30sejrqe4m.dlg@40tude.net> <87hbmae33k.fsf@ludovic-brenta.org> <85j595F1lqU1@mid.individual.net> <87sk5navk6.fsf_-_@ludovic-brenta.org> <82bpc8s17m.fsf@stephe-leake.org> <82eih2rblr.fsf@stephe-leake.org> <82fx1hr7pl.fsf@stephe-leake.org> <82fx1gafu0.fsf@stephe-leake.org> Date: Wed, 26 May 2010 03:30:47 -0400 Message-ID: <82zkzn5dco.fsf@stephe-leake.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (windows-nt) Cancel-Lock: sha1:DyoFi+zwa6tjg2N7Mk7p1oDh9aw= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@flashnewsgroups.com Organization: FlashNewsgroups.com X-Trace: d2a3c4bfcce39e197caa701199 Xref: g2news1.google.com comp.lang.ada:11032 Date: 2010-05-26T03:30:47-04:00 List-Id: Simon Wright writes: > Stephen Leake writes: > >> I often find the stack trace from a multitasking program to be pretty >> useless. The real problem is in some inner task, but the stack trace >> you get is from the environment task. >> >> That's when you have to write code to have each task dump its own >> stack when it dies. > > Unless you add (as I said above) > > GNAT.Exception_Traces.Trace_On > (Kind => GNAT.Exception_Traces.Unhandled_Raise); > > I think this may not work as advertised (or, possibly more annoying, may > be unreliable) on older GNATs. The description of that feature makes no mention of tasking. I'll have to try it. -- -- Stephe