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!news3.google.com!feeder2.cambriumusenet.nl!feeder1.cambriumusenet.nl!feed.tweaknews.nl!193.201.147.68.MISMATCH!feeder.news-service.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Symbolic tracebacks on Debian Date: Mon, 24 May 2010 20:14:50 +0100 Organization: A noiseless patient Spider Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Date: Mon, 24 May 2010 19:14:50 +0000 (UTC) Injection-Info: mx03.eternal-september.org; posting-host="KCXegvZb5vh43D+f3BR6Ew"; logging-data="13284"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+wyZzwh+xohIKE4+FJbsY27OxSbFEtYWs=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (darwin) Cancel-Lock: sha1:w+XoSjTwK5I0Xdod3jXT3v/DV0M= sha1:wSikF+oux4mJyfX3KFCSAFDkCoA= Xref: g2news2.google.com comp.lang.ada:11930 Date: 2010-05-24T20:14:50+01:00 List-Id: Stephen Leake writes: > Simon Wright writes: > >> "(see below)" writes: >> >>> Are these features enabled in your OS X port, Simon? >> >> That was a prerelease 4.5.0 -- presently running with my build of the >> official GCC release. >> >> So far as I know, these features are the same.. yes, just tried it. >> >> The tracebacks you get with atos are rather opaque, and the tool is too >> stupid to work out the architecture for itself .. >> >> $ atos -o t -arch x86_64 0x100001577 0x10000141b >> _ada_t (in t) (t.adb:16) >> main (in t) (b~t.adb:196) > > Good enough for emacs to find and display the source location, which is > all you really need. I agree about that one, but the next (from the task which died with an unhandled exception) was $ atos -o t -arch x86_64 0x100001742 0x10000aa82 0x7fff825fb8b4 t__tTKB.2815 (in t) + 86 system__tasking__stages__task_wrapper (in t) + 418 0x7fff825fb8b4 I dare say a less trivia example would work better.