Steve Tuckner wrote:
First of all I want to congratulate all who chipped in on the FreeRide
project. The more I use it the better it looks!
Of course, one of the biggest advantages of FreeRIDE is that it is written
in Ruby and is extended by creating Ruby plugins!
OK now the debugger is working with no asserts coming out.
- How does one set breakpoints. The breakpoint button does nothing.
In the edit window, double-click in the left margin of the desired line of
- How do I display the values of variables? I can see global
not local ones. I can do eval to display anything but was
wondering about a
list like the globals pane.
- The threads pane is always all gray. What is suppossed to be
- The frames pane shows different threads in a pulldown, but I don’t know
what else is supposed to be shown here.
I have claim some ignorance here as I am not the author of the debugger and
I am a Windows user where the debugger does not currently work. The best
thing would be to post these questions to the FreeRIDE Users mailing list
and let Laurent respond:
- What version of FXRuby is required for this version? 1.0.22?
Version 1.0.19 or higher should work.
- The ripper display only updates after switching to and from another
source pane. Is this a bug?
I’m not sure, Rich could have done this intentionally to minimize the
performance hit. We are planning to replace ripper with another parser and,
at least down the road, we would want the source tree to update dynamically.
It would be good if you could enter a bug report on this at:
- When doing a run to cursor I get an exception displayed in the console
pane that is below:
file' for nil (NameError) from ./plugins/rubyide_tools_debugger/debuggee.rb:1232:inprintf’
check_break_points' from ./plugins/rubyide_tools_debugger/debuggee.rb:761:in each from ./plugins/rubyide_tools_debugger/debuggee.rb:761:incheck_break_points’
I haven’t heard this one yet, please report it as a bug.
I am not opposed to hacking on the code, but am just curious about what is
known to be working/not working.
Hack away! Just be sure to send us any fixes that you make.
You can always see what problems are known/unknown and who is working to fix
what by looking at the bug list at: