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: a07f3367d7,fea50f781bb229dc
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news4.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "(see below)" <yaldnif.w@blueyonder.co.uk>
Newsgroups: comp.lang.ada
Subject: Re: Symbolic tracebacks on Debian
Date: Sat, 22 May 2010 12:03:20 +0100
Message-ID: <C81D7888.14413C%yaldnif.w@blueyonder.co.uk>
References: <xpapqc7al1kx$.10dcevapcbh68.dlg@40tude.net>
 <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>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Trace: individual.net FGG+oYoRheuOE0qbC6MmEwp8EE7OwvRpr1ITm7IqIpDikkPblw
Cancel-Lock: sha1:t6yMB9N1ZJhHsfYP0kWwgGLtL3g=
User-Agent: Microsoft-Entourage/12.23.0.091001
Thread-Topic: Symbolic tracebacks on Debian
Thread-Index: Acr5nmNS4K/UHeOW0kOio3nWFaueCQ==
Xref: g2news2.google.com comp.lang.ada:11875
Date: 2010-05-22T12:03:20+01:00
List-Id: <comp.lang.ada>

On 21/05/2010 09:52, in article 82bpc8s17m.fsf@stephe-leake.org, "Stephen
Leake" <stephen_leake@stephe-leake.org> wrote:

> Ludovic Brenta <ludovic@ludovic-brenta.org> writes:
> 
>> On the other hand,
>> since nobody noticed or reported this problem before you and gnat-4.3
>> has been in Debian since 2008-01-30, I'm starting to wonder whether
>> symbolic tracebacks are all that useful.
> 
> Because symbolic traceback are not supported on _all_ gnat platforms, I
> don't use them on _any_ - that way my code is portable. So I did not
> notice this problem.
> 
> I dump the stack trace as hex addresses, then later run addr2line
> manually if I want the symbolic trace.

Can you say exactly what the steps are to do that?
I've never understood it + therefore never used it.

-- 
Bill Findlay
<surname><forename> chez blueyonder.co.uk