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.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,d5b211b0c1ffcf3e X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Received: by 10.68.234.38 with SMTP id ub6mr628876pbc.2.1340306332381; Thu, 21 Jun 2012 12:18:52 -0700 (PDT) Path: l9ni4205pbj.0!nntp.google.com!news1.google.com!goblin3!goblin1!goblin.stu.neva.ru!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: "J-P. Rosen" Newsgroups: comp.lang.ada Subject: Re: Practicalities of Ada for app development Date: Thu, 21 Jun 2012 21:18:52 +0200 Organization: A noiseless patient Spider Message-ID: References: <79c5c9f7-4b72-4990-8961-b3e2db4db79b@qz1g2000pbc.googlegroups.com> Mime-Version: 1.0 Injection-Date: Thu, 21 Jun 2012 19:18:51 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="cJo7kSTQUrCFv2/D8KKtqw"; logging-data="9295"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+gjUuHPm22v6QqavcScUnB" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 In-Reply-To: Cancel-Lock: sha1:gKH8rW3iJH6gJ/g5MZiiVTFxkLM= X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Date: 2012-06-21T21:18:52+02:00 List-Id: Le 21/06/2012 20:16, Adam Beneschan a �crit : > Well, since I do get a lot of use out of debuggers, the assertion in > the second half of your sentence is demonstrably false. I don't > understand it, either. Why would a compiler, or a compiler's tools, > be of such a substantially different nature than other programs, that > would make a debugger useful in one situation and useless in another? Here is my typical use case. Sometimes, AdaControl encounters an unexpected combination of constructs, and generally fails with an Asis message saying "improper element". The exception message tells me where it happens, but generally the problem is slightly above, in the query that produced the invalid value. I just add a trace message at this query (I also have an integrated trace facility in AdaControl), and rerun the program. In general, I get /thousands/ of useless messages (and I can't predict how many) before the one I'm interested in, that is, the last one before the crash. I don't care, I just let the screen scroll... How could I do that in a debugger? A breakpoint, and thousands of useless "go" commands? No thanks. -- J-P. Rosen Adalog 2 rue du Docteur Lombard, 92441 Issy-les-Moulineaux CEDEX Tel: +33 1 45 29 21 52, Fax: +33 1 45 29 25 00 http://www.adalog.fr