From: RichardOnRails <RichardDummyMailbox58407@...>
Date: 2008-01-04T17:10:04+09:00
Subject: Re: Ruby-Debugger newbie problem

On Jan 4, 1:40 am, "s.ross" <cwdi...@gmail.com> wrote:
> >> 10:require 'rubygems'
> >> (rdb:1) l
> >> [5, 14] in K:/_Utilities/Ruby_1.8.2-15/ruby/lib/ruby/site_ruby/1.8/
> >> ubygems.rb
> >>   5  # All rights reserved.
> >>   6  # See LICENSE.txt for permissions.
> >>   7  #++
> >>   8
> >>   9
> >> => 10  require 'rubygems'
> >> (rdb:1)
>
> > OK, I see that I stopped at ubygems.rb:10
>
> > Question 1:  Why did the debugger stop there and not continue with
> > statements 3& 4 in my test program?  Is my Ruby installation messed
> > up?
>
> > Q 2: Why do I have a "upygems.rb" in my installation that has nothing
> > substantive than "require 'rubygems'"?
>
> > Q 3. Does the presence of this strangely named file "upygems.rb"
> > suggest my Ruby installation is messed up?
>
> > I continued the processing from the current point as shown below.
>
> > Q 4. Since I put a breakpoint at "upygems.rb:3", why didn't the
> > debugger stop there instead of running through the entire remainder of
> > the test program?
>
> > Thanks again in advance for any insights you may offer.
>
> > Regards,
> > Richard
>
> I'll take a guess.
>
> Somewhere in your environment, you have the RUBY_OPTS variable set to -
> rubygems. What does that do? It makes is so that when you type:
>
> ruby myprogram.rb
>
> the effect is:
>
> ruby -rubygems myprogram.rb
>
> Note that what you are really telling Ruby is to load your program,
> require 'ubygems' and then start.
>
> It turns out ubygems.rb is a stub file to make the command line nicer
> (who wants to type ruby -rrubygems?)
>
> Why you are getting hung up where you are is probably because that's
> the first line that can possibly be executed, the others being
> comments or whitespace. That's my guess, at least.
>
> If you just type 'c' and press enter, your program will continue
> merrily along.
>
> How close did I get?
>
>

Thanks for responding!

> Somewhere in your environment, you have the RUBY_OPTS variable set to -
> rubygems.

You've got 100% so far :-)

> What does that do? [snip]
Wow: Still at 100% with a great explanation

> Why you are getting hung up where you are is probably because that's
> the first line that can possibly be executed, the others being
> comments or whitespace. That's my guess, at least.

Sounds to me like 100% is holding!

> If you just type 'c' and press enter, your program will continue
> merrily along.
>
> How close did I get?

Perfect score ... except for one issue:  When I pressed C,  the
debugger ran through the remaining statements of the test file,
not withstanding that I had set a breakpoint, as I documented at the
end of my second post.

Again,  thanks for a great response.

Best wishes,
Richard