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
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: =?UTF-8?Q?Bj=c3=b6rn_Lundin?= <b.f.lundin@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Exception traceback when using TDM-GCC 5.1.0-3
Date: Thu, 28 Jul 2016 22:55:12 +0200
Organization: A noiseless patient Spider
Message-ID: <nndrel$t4u$1@dont-email.me>
References: <f253920a-ce9d-4786-9565-312ef6694f5a@googlegroups.com>
 <lyeg6h7wjq.fsf@pushface.org> <nn56dc$2q4$1@dont-email.me>
 <bf2a2a66-66f3-4efe-9544-bdf86df3beba@googlegroups.com>
 <66240de6-d3a8-458d-9eb9-1214f790831c@googlegroups.com>
 <lyoa5jjzy9.fsf@pushface.org>
 <e54debdd-d993-4008-a652-a5f027479995@googlegroups.com>
 <lypopz5i71.fsf@pushface.org>
 <e383d5f2-2736-4d89-af40-3940b2e008b8@googlegroups.com>
 <lylh0n5bkh.fsf@pushface.org>
 <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>
 <c0c8ac31-8250-4b4c-8b4f-f6b893c43802@googlegroups.com>
 <d30b5ac6-8d14-441c-b6a9-28165c6337aa@googlegroups.com>
 <8a97f7ff-7fda-480b-9f6e-68a4f2995b83@googlegroups.com>
 <26fc8fd2-f81b-45f6-a584-e8558239eae0@googlegroups.com>
 <1114393d-a298-4b49-bae8-43ded7879887@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 28 Jul 2016 20:54:45 -0000 (UTC)
Injection-Info: mx02.eternal-september.org;
 posting-host="a5aaa847a1537eed2ffee86793c93776";
	logging-data="29854"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18KX/kgRA4t22G6RlRx89Wv"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Icedove/38.7.0
In-Reply-To: <1114393d-a298-4b49-bae8-43ded7879887@googlegroups.com>
Cancel-Lock: sha1:6zN0UhJiDFuDhekONe9fn5Tr5x0=
Xref: news.eternal-september.org comp.lang.ada:31208
Date: 2016-07-28T22:55:12+02:00
List-Id: <comp.lang.ada>

On 2016-07-28 22:34, ahlan.marriott@gmail.com wrote:

> Björn 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örn does.
> GNAT.Traceback.Symbolic.Symbolic_Traceback worked for me using Gnat Pro and GPL so I rather hoped it would work using TDM.


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)

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.

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.


--
Björn