Step into/over not working in Netbeans with ruby 2.0

[ruby-debug]

Step into/over not working in Netbeans with ruby 2.0

[rockorequin]

More concisely, what happens with ruby-2.0/debase-0.0.3 is that every time the thread hits a breakpoint and suspends, debase reports back first 'suspend' then 'breakpoint' for the same line. Whereas ruby-1.9/ruby-debug-base19x always reports exactly one event: if the thread was running and it hits a breakpoint, it reports only 'breakpoint'; if the thread was being stepped and the step finishes, it reports 'suspend'.

This confuses the Netbeans plugin because it only ever expects only one event when the thread suspends - it treats the 'breakpoint' and 'suspend' events exactly the same. So it ends up locking a semaphore twice for essentially what is the same event, and when the user issues a command to step or continue, it only releases the semaphore once and subsequently freezes.

[rockorequin]

If I comment out this line in debase's ext/debase_internals.c#process_line_event function:

    rb_funcall(context_object, idAtBreakpoint, 1, breakpoint); 

the ruby-netbeans plugin runs without problem.

This makes debase only send suspend events, ie it never sends breakpoint events, so it doesn't exactly mimic the behaviour of ruby-debug-base19x. So the question still is, should debase mimic ruby-debug-base19x's behaviour? Modifying the ruby-netbeans plugin to handle the current debase-0.0.3 behaviour is a bit complex unless we change it to just ignore all breakpoint events from any version of ruby greater than 1.9.

[denofevil]

Yes, it looks like behaviour is slightly different compared with ruby-debug-base19x. I'll test version with commented breakpoint event on RubyMine and will upload it if everything is ok

[rockorequin]

How did it go in RubyMine?

[denofevil]

The real problem was in debase not setting correct stop reason when hitting breakpoint. You can try debase-0.0.4, it should work ok now.

[rockorequin]

Thanks, debase-0.0.4 does work now in Netbeans.