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.224.188.8 with SMTP id cy8mr1879514qab.6.1340313312832; Thu, 21 Jun 2012 14:15:12 -0700 (PDT) Path: l9ni4508pbj.0!nntp.google.com!news1.google.com!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 23:15:12 +0200 Organization: A noiseless patient Spider Message-ID: References: <79c5c9f7-4b72-4990-8961-b3e2db4db79b@qz1g2000pbc.googlegroups.com> <92daaca1-46ae-43e1-abae-397b4bf6aa33@googlegroups.com> Mime-Version: 1.0 Injection-Date: Thu, 21 Jun 2012 21:15:12 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="cJo7kSTQUrCFv2/D8KKtqw"; logging-data="22651"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19Z+cpeIz7CnbyzOmzYo1B0" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 In-Reply-To: <92daaca1-46ae-43e1-abae-397b4bf6aa33@googlegroups.com> Cancel-Lock: sha1:E3ZFvBWPhmYMxvY+tETkSQK9sRU= X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Date: 2012-06-21T23:15:12+02:00 List-Id: Le 21/06/2012 22:30, Adam Beneschan a �crit : > Actually, that's a typical case where I find a debugger useful. At > the point where you add the trace message, I set a breakpoint, but > set it up so that it continues automatically and doesn't display any > message. Then when the crash occurs, I ask the debugger to display > information on the breakpoint, and find that it occurred N times. > Then I rerun the program, and set a breakpoint at that same place, > telling the debugger to stop the program after it's hit that place > N-1 times. That way, I can see what's going on just before the > crash. I do that sort of thing quite frequently. Of course, it only > works if you can duplicate the run exactly, which isn't always going > to be possible with some nondeterministic programs that depend on > external events. So, you have to run the program twice while I need only once. OTOH, once you have the proper breakpoint, you could investigate more stuff. But in my case (YMMV), my trace produces enough information, and there is not much I could get from the debugger (ASIS elements are private types of the implementation of ASIS - which I don't know, therefore there isn't much I can learn from browsing them. My trace provides higher level information) -- 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