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,d5b211b0c1ffcf3e
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.193.129 with SMTP id ho1mr2027351pbc.8.1340341150315;
        Thu, 21 Jun 2012 21:59:10 -0700 (PDT)
Path: 
 l9ni5681pbj.0!nntp.google.com!news2.google.com!goblin2!goblin1!goblin.stu.neva.ru!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Practicalities of Ada for app development
Date: Fri, 22 Jun 2012 05:59:08 +0100
Organization: A noiseless patient Spider
Message-ID: <m2wr30ymar.fsf@pushface.org>
References: 
 <79c5c9f7-4b72-4990-8961-b3e2db4db79b@qz1g2000pbc.googlegroups.com>
	<jqtr7u$3r9$1@adenine.netfront.net>
	<f33223ab-5c08-40f5-b0ee-a57862ce72f5@googlegroups.com>
	<jqur16$teu$1@adenine.netfront.net> <jrvkq7$qc8$1@munin.nbi.dk>
	<afa4c8e4-dba8-460c-877b-a848255c4572@googlegroups.com>
	<jrvs2r$92f$1@dont-email.me>
	<92daaca1-46ae-43e1-abae-397b4bf6aa33@googlegroups.com>
	<js02ij$eb8$1@munin.nbi.dk>
Mime-Version: 1.0
Injection-Info: mx04.eternal-september.org;
 posting-host="6Tbb1TGS9uC8f8w5kfXwXw";
	logging-data="29886"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+ycKj13WY9nQcNyP62tpdhFhzAe7mAMtM="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (darwin)
Cancel-Lock: sha1:H0spO25qQjr+0isxGdRXzFz5dOM=
	sha1:JF5YB643BIgt2OZj6ztVWAAW3CQ=
Content-Type: text/plain
Date: 2012-06-22T05:59:08+01:00
List-Id: <comp.lang.ada>

"Randy Brukardt" <randy@rrsoftware.com> writes:

> "Adam Beneschan" <adam@irvine.com> wrote in message 
> news:92daaca1-46ae-43e1-abae-397b4bf6aa33@googlegroups.com...
> ...
>> 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.
>
> I've never encountered any debugger that even claimed to have that
> information; I've surely never used one that has any sort of count or
> other information about a breakpoint (other than the address where it
> is set).  They just break, period.

GDB does this.

(gdb) catch exception constraint_error
Catchpoint 1: `constraint_error' Ada exception
(gdb) commands 1
>continue
>end
(gdb) run
[lots of output]
(gdb) info breakpoints
Num     Type           Disp Enb Address            What
1       breakpoint     keep y   0x0000000100025fd7 `constraint_error' Ada exception
	breakpoint already hit 5 times
        continue