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: 103376,93a8020cc980d113 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Newsgroups: comp.lang.ada Subject: Re: What is wrong with Ada? References: <1176150704.130880.248080@l77g2000hsb.googlegroups.com> <461B52A6.20102@obry.net> <461BA892.3090002@obry.net> <82dgve.spf.ln@hunter.axlog.fr> <1176226291.589741.257600@q75g2000hsh.googlegroups.com> <2tabxgm6jy.fsf@hod.lan.m-e-leypold.de> <877iskdqz0.fsf@ludovic-brenta.org> From: Markus E Leypold Organization: N/A Date: Tue, 10 Apr 2007 22:22:58 +0200 Message-ID: User-Agent: Some cool user agent (SCUG) Cancel-Lock: sha1:JVjHaBSGYlNpd7iyqR6PRD4u7C0= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NNTP-Posting-Host: 88.72.227.169 X-Trace: news.arcor-ip.de 1176236140 88.72.227.169 (10 Apr 2007 22:15:40 +0200) X-Complaints-To: abuse@arcor-ip.de Path: g2news1.google.com!news3.google.com!out02a.usenetserver.com!news.usenetserver.com!in01.usenetserver.com!news.usenetserver.com!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.arcor-ip.de!news.arcor-ip.de!not-for-mail Xref: g2news1.google.com comp.lang.ada:14889 Date: 2007-04-10T22:22:58+02:00 List-Id: Ludovic Brenta writes: > Markus E Leypold writes: >> Which reminds me, that I wished that the compiler and the debugger >> would work well enough together that I could just say: I now want a >> trace (including parameters) of every call to modules M, M', ... and >> would get it without too much fiddling. This is in my eyes what >> debuggers are (should be) good for. > > Look into DTraq: http://www.mckae.com/dtraq.html > > Never used it myself, but it seems to be what you want. Thank you, > ASIS, and thank you, McKae Technologies. Indeed that is very near. In practice it would suffice. But I meant was actually different, i.e. that one doesn't need to change the executable at all (DTraq only automates the instrumentation as I understand it). The debugger has all means available to inspect the application memory, the compiler could provide layout and type information. That should suffice to "tap" even uninstrumented executables automatically (but requires tighter integration with the compiler). Regards -- Markus