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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.159.35.84 with SMTP id 78mr33311805uae.0.1469774414241; Thu, 28 Jul 2016 23:40:14 -0700 (PDT) X-Received: by 10.157.10.1 with SMTP id 1mr2567729otg.12.1469774414200; Thu, 28 Jul 2016 23:40:14 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!c52no5657589qte.1!news-out.google.com!d130ni17938ith.0!nntp.google.com!f6no5603996ith.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 28 Jul 2016 23:40:13 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2a02:1205:c68c:9d90:ed14:431d:9fbe:4867; posting-account=Pm0FhgoAAAAiPscNT3etSZ15tHNZGXm_ NNTP-Posting-Host: 2a02:1205:c68c:9d90:ed14:431d:9fbe:4867 References: <66240de6-d3a8-458d-9eb9-1214f790831c@googlegroups.com> <22f2e37f-dc90-42ce-a6d3-42f0a471c4d6@googlegroups.com> <6178bf6c-6125-43b2-86c4-aeb08be48442@googlegroups.com> <273d77a5-55a6-4de6-abbe-93bb61ecfdc3@googlegroups.com> <4bd0a4ff-8262-41ee-bb5c-23672206a59a@googlegroups.com> <8a97f7ff-7fda-480b-9f6e-68a4f2995b83@googlegroups.com> <26fc8fd2-f81b-45f6-a584-e8558239eae0@googlegroups.com> <1114393d-a298-4b49-bae8-43ded7879887@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <737eb192-86eb-4c09-9b60-759ae29987f2@googlegroups.com> Subject: Re: Exception traceback when using TDM-GCC 5.1.0-3 From: ahlan.marriott@gmail.com Injection-Date: Fri, 29 Jul 2016 06:40:14 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:31214 Date: 2016-07-28T23:40:13-07:00 List-Id: On Thursday, 28 July 2016 22:54:46 UTC+2, bj=C3=B6rn lundin wrote: > On 2016-07-28 22:34, ahlan.marriott@gmail.com wrote: >=20 > > Bj=C3=B6rn has a work around foo this problem - but surely this shouldn= 't be necessary. > > Surely the whole point of GNAT.Traceback.Symbolic.Symbolic_Traceback is= to save having to do what Bj=C3=B6rn does. > > GNAT.Traceback.Symbolic.Symbolic_Traceback worked for me using Gnat Pro= and GPL so I rather hoped it would work using TDM. >=20 >=20 > The reason we do it via addr2line is that once (say 10 years ago) > I complained to then ACT that the stacktrace does not produce correct > results on aix. we got traces, but sometimes totally wrong (as in row > num 658425 in a file with 2000 rows) >=20 > ACT then said that getting a reliable stacktrace from a dying process > was no good idea. So we just get the hex-dump, and then spawns > addr2line. This we do with Gnat pro and gnat gpl. >=20 > I do have noticed that for gnat fsf on linux x64, we sometimes get no > trace when passing the exception_occurence to a procedure in another > package. >=20 >=20 > -- > Bj=C3=B6rn Dear Bj=C3=B6rn, Thanks for the info. Although I would have thought trying to spawn a new process and pipe inform= ation to it from a dying process would have been a even less of a good idea= ;-) MfG Ahlan