RE: [FR-devel] Troubles running FR on Win32

[Curt Hibbs]

Laurent Julliard wrote:
>
> The symptoms are not the same on both platforms (at least from what I
> see on Command window). On Win2k the command when ran says it cannot
> load plugins/Debugger/debuggee.rb and when I type the exact same
> command on the Command window it works well.
>
> I'm really stuck here and any help you can provide me with, including
> testing on your own Windows machine is more than welcome.

Its possible that the current working directory is not what you expect it to
be and is, in fact, different on each OS.

I just tried debugging hello.rb. When I edit/debug it from the
R:\ruby-172\samples directory I get this in the command window:


R:\freeride>run

R:\freeride>ruby -I. -Iso -Iredist -e "require 'freeride/freeride';
FreeBASE::Core.startup('./config
/properties.xml','./config/default.xml')"
redist/log4r/repository.rb:55: warning: parenthesize argument(s) for future
version
redist/log4r/configurator.rb:72: warning: parenthesize argument(s) for
future version
redist/log4r/configurator.rb:72: warning: parenthesize argument(s) for
future version
redist/log4r/configurator.rb:78: warning: parenthesize argument(s) for
future version
redist/log4r/configurator.rb:138: warning: parenthesize argument(s) for
future version
redist/log4r/configurator.rb:180: warning: parenthesize argument(s) for
future version
1, 1,1,1
sep: /
ruby -I. -Iso -Iredist -r./plugins/Debugger/debuggee.rb
R:\ruby-172\samples\hello.rb
#<IO:0x33fcc08>
#<IO:0x33fcc08>
R:\ruby-172\samples\hello.rb on druby://L5:1386 attached.
#<IO:0x33fcc08>
#<IO:0x33fcc08>
#<IO:0x33fcc08>
#<IO:0x33fcc08>
#<IO:0x33fcc08>
#<IO:0x33fcc08>
Debug.rb
Emacs support available.

R:/ruby-172/samples/hello.rb:1:

At this point everything is frozen and I have to kill FreeRIDE.

Ok, I'm going to show my Ruby ignorance now... I've never yet used the ruby
debugger, so I don't know what I should expect (that is, what is the normal
behavior). Should I have gvotten a prompt in my command window where I
should have been able to enter debugger commands?

Curt