ANN: FreeRIDE 0.5.0 Final Release

Steve Tuckner wrote:

I downloaded the release candidate and ran it in its directory and
there seemed to be no debugger present.

If it doesn’t work, is there any way I could help in getting it working?

It looks like the debugger plugin has its autoload property set false. Edit
the file:

.../freeride/plugins/rubyide_tools_debugger/plugin.yaml

and change the line “autoload: false” to “autoload: true”.

I guess I better put this on the wiki.

Curt

Curt Hibbs wrote:

It looks like the debugger plugin has its autoload property set
false. Edit
the file:

…/freeride/plugins/rubyide_tools_debugger/plugin.yaml

and change the line “autoload: false” to “autoload: true”.

Turns out you also have to set “autoload: true” in:

.../freeride/plugins/rubyide_tools_fox_debugger/plugin.yaml

Curt

Thanks Curt for those pointers. My debugger now functions (hurrah!)…but

When I start the debugger I get displayed over an over

FXRuby.cpp:647: FXASSERT(FALSE) failed.

The debugger works however. Except that I can’t set breakpoints. Clicking on
the breakpoint button did nothing.

So…I thought maybe my version of FXRuby needed to be updated. My version
was 1.0.19 and the current is 1.0.22. I got 1.0.22 and tried to follow the
instructions from Lyle to build it with FXScintilla support (see below):

  1. Type ‘ruby install.rb config [… options …]’
    to configure the build, and be sure to pass in the
    ‘–with-fxscintilla-include’ and ‘–with-fxscintilla-lib’
    options.

However I am doing something wrong, because when I type:

ruby install.rb config --with-fxscintilla-include --with-fxscintilla-lib

and it says that those are invalid options.

I am now stuck because I did build and install 1.0.22 without the fx
scintilla options and so free ride no longer runs.

HEEEEEEEEEEEEEEEEELP!

Steve Tuckner

···

-----Original Message-----
From: Curt Hibbs [mailto:curt@hibbs.com]
Sent: Tuesday, April 29, 2003 2:29 AM
To: ruby-talk ML
Subject: Re: ANN: FreeRIDE 0.5.0 Final Release

Curt Hibbs wrote:

It looks like the debugger plugin has its autoload property set
false. Edit
the file:

.../freeride/plugins/rubyide_tools_debugger/plugin.yaml

and change the line “autoload: false” to “autoload: true”.

Turns out you also have to set “autoload: true” in:

…/freeride/plugins/rubyide_tools_fox_debugger/plugin.yaml

Curt

Steve Tuckner wrote:

Thanks Curt for those pointers. My debugger now functions (hurrah!)…but

When I start the debugger I get displayed over an over

FXRuby.cpp:647: FXASSERT(FALSE) failed.

The debugger works however. Except that I can’t set breakpoints.
Clicking on
the breakpoint button did nothing.

My fault here – there are actually two plugins that need autoload set to
true:

.../freeride/plugins/rubyide_tools_debugger/plugin.yaml
.../freeride/plugins/rubyide_tools_fox_debugger/plugin.yaml

Also, please note that debugger only works under Linux, we are still
struggling to get it working under Windows.

So…I thought maybe my version of FXRuby needed to be updated. My version
was 1.0.19 and the current is 1.0.22. I got 1.0.22 and tried to follow the
instructions from Lyle to build it with FXScintilla support (see below):

  1. Type ‘ruby install.rb config [… options …]’
    to configure the build, and be sure to pass in the
    ‘–with-fxscintilla-include’ and ‘–with-fxscintilla-lib’
    options.

However I am doing something wrong, because when I type:

ruby install.rb config --with-fxscintilla-include
–with-fxscintilla-lib

and it says that those are invalid options.

I am now stuck because I did build and install 1.0.22 without the fx
scintilla options and so free ride no longer runs.

HEEEEEEEEEEEEEEEEELP!

Try:
ruby install.rb config –
–with-fxscintilla-include=/usr/local/include/fxscintilla
–with-fxscintilla-lib=/usr/local/lib

Curt

First of all I want to congratulate all who chipped in on the FreeRide
project. The more I use it the better it looks!

OK now the debugger is working with no asserts coming out.

But…

  1. How does one set breakpoints. The breakpoint button does nothing.
  2. How do I display the values of variables? I can see global variables but
    not local ones. I can do eval to display anything but was wondering about a
    list like the globals pane.
  3. The threads pane is always all gray. What is suppossed to be shown here?
  4. The frames pane shows different threads in a pulldown, but I don’t know
    what else is supposed to be shown here.
  5. What version of FXRuby is required for this version? 1.0.22?
  6. The ripper display only updates after switching to and from another
    source pane. Is this a bug?
  7. When doing a run to cursor I get an exception displayed in the console
    pane that is below:

(druby://tuckmiester:2694)
./plugins/rubyide_tools_debugger/debugger.rb:454:in ‘printf’:undefined
method file' for nil (NameError) from ./plugins/rubyide_tools_debugger/debuggee.rb:1232:in printf’
from ./plugins/rubyide_tools_debugger/debuggee.rb:764:in
check_break_points' from ./plugins/rubyide_tools_debugger/debuggee.rb:761:in each from ./plugins/rubyide_tools_debugger/debuggee.rb:761:in check_break_points’
from ./plugins/rubyide_tools_debugger/debuggee.rb:870:in `trace_func’
from ./plugins/rubyide_tools_debugger/debuggee.rb:1381
from ./plugins/rubyide_tools_debugger/debuggee.rb:1382
from /home/sat/Build/freeride-0.5.0/test1.rb:4

I am not opposed to hacking on the code, but am just curious about what is
known to be working/not working.

Thanks for all the great work! :-))

Steve Tuckner

···

-----Original Message-----
From: Curt Hibbs [mailto:curt@hibbs.com]
Sent: Tuesday, April 29, 2003 11:30 AM
To: ruby-talk ML
Subject: Re: ANN: FreeRIDE 0.5.0 Final Release

Steve Tuckner wrote:

Thanks Curt for those pointers. My debugger now functions
(hurrah!)…but

When I start the debugger I get displayed over an over

FXRuby.cpp:647: FXASSERT(FALSE) failed.

The debugger works however. Except that I can’t set breakpoints.
Clicking on
the breakpoint button did nothing.

My fault here – there are actually two plugins that need
autoload set to
true:

…/freeride/plugins/rubyide_tools_debugger/plugin.yaml
…/freeride/plugins/rubyide_tools_fox_debugger/plugin.yaml

Also, please note that debugger only works under Linux, we are still
struggling to get it working under Windows.

So…I thought maybe my version of FXRuby needed to be
updated. My version
was 1.0.19 and the current is 1.0.22. I got 1.0.22 and
tried to follow the
instructions from Lyle to build it with FXScintilla support
(see below):

  1. Type ‘ruby install.rb config [… options …]’
    to configure the build, and be sure to pass in the
    ‘–with-fxscintilla-include’ and ‘–with-fxscintilla-lib’
    options.

However I am doing something wrong, because when I type:

ruby install.rb config --with-fxscintilla-include
–with-fxscintilla-lib

and it says that those are invalid options.

I am now stuck because I did build and install 1.0.22 without the fx
scintilla options and so free ride no longer runs.

HEEEEEEEEEEEEEEEEELP!

Try:
ruby install.rb config –
–with-fxscintilla-include=/usr/local/include/fxscintilla
–with-fxscintilla-lib=/usr/local/lib

Curt

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!

Thanks!

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.

But…

  1. 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
code.

  1. How do I display the values of variables? I can see global
    variables but
    not local ones. I can do eval to display anything but was
    wondering about a
    list like the globals pane.
  2. The threads pane is always all gray. What is suppossed to be
    shown here?
  3. 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:

http://savannah.nongnu.org/mail/?group=freeride

  1. What version of FXRuby is required for this version? 1.0.22?

Version 1.0.19 or higher should work.

  1. 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:

http://savannah.nongnu.org/bugs/?func=addbug&group=freeride

  1. When doing a run to cursor I get an exception displayed in the console
    pane that is below:

(druby://tuckmiester:2694)
./plugins/rubyide_tools_debugger/debugger.rb:454:in ‘printf’:undefined
method file' for nil (NameError) from ./plugins/rubyide_tools_debugger/debuggee.rb:1232:in printf’
from ./plugins/rubyide_tools_debugger/debuggee.rb:764:in
check_break_points' from ./plugins/rubyide_tools_debugger/debuggee.rb:761:in each from ./plugins/rubyide_tools_debugger/debuggee.rb:761:in check_break_points’
from ./plugins/rubyide_tools_debugger/debuggee.rb:870:in
`trace_func’
from ./plugins/rubyide_tools_debugger/debuggee.rb:1381
from ./plugins/rubyide_tools_debugger/debuggee.rb:1382
from /home/sat/Build/freeride-0.5.0/test1.rb:4

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:

http://savannah.nongnu.org/bugs/?group=freeride

Curt