Re: Enabling a breakpoint after another breakpoint has been visitied/hit

A variation of this has been entered into the bug database last year. It 
is a P2, which means it will get done in an upcoming release. However, 
that will likely be a couple of months given the current pace. Feel free 
to vote on the request, and/or submit a patch.

http://www.bluemarsh.com/bugzilla/show_bug.cgi?id=984

Thanks

n


Kristian Waagan wrote:
> Hello,
> 
> JSwat is a very nice application! Thanks :)
> 
> I wonder if it is possible to add the feature to enable a breakpoint 
> only after another breakpoint has been visitied/hit (n times). This is 
> nice when you have an application that takes the same code path numerous 
> times, but you are only interested in studying the breakpoint after a 
> certain point.
> 
> I have used both the "enable after n visits" and simply disabling the 
> breakpoint as work-arounds. When I reach the "barrier breakpoint", I 
> then enable the first breakpoint manually. Although this works fine, it 
> is tedious to disable the breakpoint after each run and then enabling it 
> again during the next run.
> 
> To illustrate:
> breakpoint A : some lower-level library code : X hits - DISABLED
> breakpoint B : some higer-level code : 1st hit - ENABLE A
> breakpoint A : : hit X+1 : ENABLED
> 
> 
> Does this make any sense?
> Is this already possible in JSwat?
> 
> 
> 
> Regards,
> -- 
> Kristian