RE: [MI tracepoints 5/9] -break-passcount

[Marc Khouzam <marc.khouzam@ericsson.com>]

> -----Original Message-----
> From: gdb-patches-owner@sourceware.org 
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Vladimir Prus
> Sent: March-16-10 1:07 PM
> To: Tom Tromey; gdb-patches@sourceware.org
> Subject: Re: [MI tracepoints 5/9] -break-passcount
> 
> On Tuesday 16 March 2010 19:23:22 Tom Tromey wrote:
> 
> > >>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:
> > 
> > Tom> It is odd to have a command named -break-passcount that can't 
> > Tom> actually be used on breakpoints
> > 
> > Volodya> It can -- just not on all kinds of breakpoints.
> > 
> > Ok.  Maybe you could explain how -break-passcount and 
> -break-after are 
> > different, without referring to "tracepoints" as something separate 
> > from "breakpoints".
> 
> -break-after specifies how many initial hits of the 
> breakpoint are to be ignored.
> 
> -break-passcount, ideally, after how many execution of 
> breakpoint commands they stop being executed (and breakpoint 
> becomes silently ignored)

It would be nice to have this new -break-passcount also work for 'normal'
breakpoints.  The use case is the following:

when setting a breakpoint in code that many threads go through, and
while debugging in non-stop mode, a user may not want every thread to stop
on the breakpoint, but only one thread (or N threads).  This is special 
to non-stop because many threads could hit in a very short amount of time,
before the user can disable the bp manually.  
With -break-passcount, we can tell GDB that "after N threads have been 
stopped on this breakpoint, disable the bp".

Thanks

Marc