This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Ability to apply breakpoint hit condition | ||
---|---|---|---|
Product: | ruby | Reporter: | Martin Krauskopf <mkrauskopf> |
Component: | Debugger | Assignee: | Martin Krauskopf <mkrauskopf> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | bleonard, gsporar, mvyver, richo |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Martin Krauskopf
2007-04-05 13:19:54 UTC
Reassigning this issue to newly created 'ruby' component. I would like to be able to set a breakpoint and then set a property on that breakpoint to only break on certain conditions (any statement written as ruby and using anything in scope at the point of breaking). Also a breakpoint that doesn't break but writes a log entry (to a custom window or file or anything), the log entry should be constructed as a ruby statement having all items in scope at the breakpoint available to it. Other breakpoint features I have used before (in other IDEs) but not as important are A) only break after x number of passes. B) Put breakpoints into groups. Then have another breakpoint be able to enable or disable the groups. This allows for breakpoints in commonly called routines to only be active once a certain other breakpoint has been hit. After evaluation, postponing this after 6.1, when I want to do overhaul in the debug-commons project and to catch up at least a little bit furiously evolving ruby-debug project. I've at least did some preparation works (trivial customizer in editor stripe and breakpoint nodes). To much works in other area which has higher priority into 6.1, sorry. Working on it in backends. Will be available with next version of ruby-debug-ide and new JRuby fast debugger. I'm planning to release both of those shortly after JRuby 1.1.2 which should be released likely around end of May. Might be I'll integrate sooner for those playing with trunk versions.... started. Setting condition is now possible (see below). Leaving this open for now, since this RFE contains more ideas. I'll either fix them as part of this issue or file few smaller ones. Commits: 3bfdd4790520, f96b1bf65f52 Commit log: Supports for setting condition (expression returning boolean) on breakpoints - one part of #100096 - in the meantime this only work with trunk versions - ruby-debug-ide 0.1.11 - JRuby 1.1.2 if using JRuby Also note you need trunk versions now, so it's not that easy to set up. Will be out-of-the box once ruby-debug-ide is out and also JRuby 1.1.2 if JRuby is used. Integrated into 'main-golden', available in NB_Trunk_Production #196 build Changeset: http://hg.netbeans.org/main/rev/3bfdd4790520 User: Martin Krauskopf <mkrauskopf@netbeans.org> Log: Supports for setting condition (expression returning boolean) on breakpoints - one part of #100096 - in the meantime this only work with trunk versions - ruby-debug-ide 0.1.11 - JRuby 1.1.2 if using JRuby I've filed other RFE separately for better tracking: issues 135138, 135139, 135140 richo I've CCed you automatically there since you came with those ideas. I believe that setting expression condition is the most useful case which is implemented in trunk. Marking this one fixed. |