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.
latest NB + fresh ruby build ------------------------------------------- have a script with d = Date.new and put a BP to this line. Start debugger, when it stops at BP, push F7 you jump on the line unless jd = valid_civil?(y, m, d, sg), push F7, nothing happens, push F7 again. Now you are on line if m < 0 you can try pushing F8, notice that on some lines, you need to F8 push more times to step over. I did not find any general rule why this sometimes happens.
As I understand, it is actually a feature "step over expression". E.g.: $ cat test1.rb n = (1 + 2) + (10 + 20) + (100 + 200) start debugger (_code_ means where we are in the execution) 1: _n = (1 + 2) + (10 + 20) + (100 + 200)_ 'step' command 1: n = _(1 + 2)_ + (10 + 20) + (100 + 200) 'step' command 1: n = (1 + 2) + _(10 + 20)_ + (100 + 200) 'step' command 1: n = (1 + 2) + (10 + 20) + _(100 + 200)_ I don't know if it is possible to obtain "in-line-range" from the backends so we could select just a part of line. Also I could provide two more actions "step+" and "next+" which would always force the debugger to go to a new line. But this would mean two more buttons in the toolbar and two more menu items. Note that I can't use "step+" and "next+" commands implicitly since I'm not able to distinguish between expressions like: puts "hi" while (i+=1) < 5 and if some_boolean_function? ... end Probably TM -> future.
In NetBeans 6 we already have separate toolbar buttons for line-stepping versus expression-stepping, since this feature has just become available for Java (because of new support in Java SE 6) - see Step Over versus Step Over Expression in the Run menu.
I exchanged email with Kent, he tried to avoid the original problem of this issue Tomas had, but it introduced another issues. Nobody knows about the fix yet in the backend. So this is 'will not fix' for now. Wrt. to Step over expression feature in Ruby we may file another Feature request for this. But currently not possible.
Reassigning this issue to newly created 'ruby' component.
Changing target milestone of all resolved Ruby issues from TBD to 6.0 Beta 1 build.
probably has to be fixed in backend, agreed with wontfix for netbeans. verified.