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=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,475d5d08fbf558a2 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!postnews.google.com!p8g2000yqb.googlegroups.com!not-for-mail From: =?ISO-8859-1?Q?Hibou57_=28Yannick_Duch=EAne=29?= Newsgroups: comp.lang.ada Subject: Re: Addr2Line2Locations for GPS Date: Sun, 17 Jan 2010 17:38:45 -0800 (PST) Organization: http://groups.google.com Message-ID: References: NNTP-Posting-Host: 77.198.58.20 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1263778725 9836 127.0.0.1 (18 Jan 2010 01:38:45 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 18 Jan 2010 01:38:45 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: p8g2000yqb.googlegroups.com; posting-host=77.198.58.20; posting-account=vrfdLAoAAAAauX_3XwyXEwXCWN3A1l8D User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; fr),gzip(gfe),gzip(gfe) Xref: g2news1.google.com comp.lang.ada:8780 Date: 2010-01-17T17:38:45-08:00 List-Id: On 16 jan, 03:25, "Randy Brukardt" wrote: > I would put links to your utilities onto AdaIC, but you need to have a we= b > page describing them somewhere so that I can do that. I don't want to mak= e > links to random .zip or .tar files from our site given the minimal > descriptions that we put there. > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Randy Brukardt, Ad= aIC webmaster Done : http://www.les-ziboux.rasama.org/addr2line2locations-tool-ada-gps-en= .html On 16 jan, 09:45, "Dmitry A. Kazakov" wrote: > [...] > Not in this form, but yes, I have done something similar for the Gtk > tracing tool. If there is a stack trace it can be cut and pasted into the > tool's box. Upon pasting address locations are replaced by the symbolic > ones. Further, when GPS is active you can right click on a symbolic trace > line and that will open in the GPS the source file selecting to > corresponding source line. So it recognizes whether the particular line i= n > the message box is a symbolic source location (e.g. file name + line > number) or else just a message text: I've also changed some stuff this way : it now parse the message which comes with the exception log, at least to add an entry for the instruction which raised the exception, which is not part of the traceback (obviously, as a Raise statement is not a subprogram call). This also now tries to automatically fill-up the exception log input field based on the text content of any active console at the moment the command is invoked (very convenient for users), and try to fill-up the executable name input field based on the project properties. If there are multiples, then the user may choose among items of a list, and he/she is still able to manually edit anyway.