Ruby debuger on Windows

[HaPK]

Can somebody point out, why on Windows
ruby -r debug my_ruby_script.rb

start in "ubygems.rb" and not in "my_ruby_script.rb". With "start" I
mean, that I expected to see the first line of _my_ file as the current
statement.

PS I'm using ruby 1.8.2-14 (2004-12-25) - installed from OneClickInstaller.

 

[Park Heesob]

Hi,
----- Original Message -----
From: "HaPK" <[email protected]>
To: "ruby-talk ML" <[email protected]>
Sent: Monday, December 05, 2005 9:00 PM
Subject: Ruby debuger on Windows

Can somebody point out, why on Windows
ruby -r debug my_ruby_script.rb

start in "ubygems.rb" and not in "my_ruby_script.rb". With "start" I mean,
that I expected to see the first line of _my_ file as the current
statement.

PS I'm using ruby 1.8.2-14 (2004-12-25) - installed from
OneClickInstaller.

That is due to RUBYOPT environment variable.

First unset RUBYOPT
and run
ruby -r debug my_ruby_script.rb

You can do it with one line
ruby -e "ENV['RUBYOPT']=nil;system('ruby -rdebug my_ruby_script.rb')"

Hope this helps,

Park Heesob

 

[HaPK]

Can somebody point out, why on Windows
ruby -r debug my_ruby_script.rb

start in "ubygems.rb" and not in "my_ruby_script.rb". With "start" I
mean, that I expected to see the first line of _my_ file as the
current statement.

PS I'm using ruby 1.8.2-14 (2004-12-25) - installed from
OneClickInstaller.

Oh... figured out myself.. The problem was in RUBY_OPT environment
variable set up to "rubygems" (multiple times: "rubygems rubygems ... "
I think its a bug in OneClickInstaller for ruby 1.8.2-14)

BTW, I had problems with Rails (actually with ActiveRecord) from version
0.14.1 with ruby 1.8.2-14.. After upgrading to 1.8.2-15 problems gone...