Enabling a breakpoint after another breakpoint has been visitied/hit
"Kristian Waagan" <[email protected]> Mon, 3 Jul 2006 22:25:03 +0200
| Newsgroups | gmane.comp.java.jswat.user |
|---|---|
| Message-ID | <[email protected]> |
--===============0671957963== Content-Type: multipart/alternative; boundary="----=_Part_73098_596860.1151958303689" ------=_Part_73098_596860.1151958303689 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 ------=_Part_73098_596860.1151958303689 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello,<br><br>JSwat is a very nice application! Thanks :)<br><br>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. <br><br>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. <br><br>To illustrate:<br>breakpoint A : some lower-level library code : X hits - DISABLED<br>breakpoint B : some higer-level code : 1st hit - ENABLE A<br>breakpoint A : : hit X+1 : ENABLED<br><br><br>Does this make any sense? <br>Is this already possible in JSwat?<br><br><br><br>Regards,<br>-- <br>Kristian<br> ------=_Part_73098_596860.1151958303689-- --===============0671957963== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ jswat-user mailing list [email protected] http://www.bluemarsh.com/mailman/listinfo/jswat-user --===============0671957963==--