> > Actually, the norm i've experienced is that, if it can't set the 
> > breakpoint where you wanted it, it either tells you it 
> couldn't set it
> > or tells you that it set it on another line, instead.   
> 
> Exactly.  In my case, I tried to set a break point on a blank 
> line.  For example, let's say my code was like
> this:
> 
> 1: # This is my Ruby code
> 2: foo = 2
> 3:
> 4: bar = 3
> 
> I did "b 3" and expected a message back from the debugger 
> like "Breakpoint set on line 4."  And then when I did "c"
> for continue, I expected execution to stop at line 4.
> But it just blazed on past lines 3 and 4.

OK, so since nobody has spoken up otherwise, let's call
this a bug in the debugger.  Since I'm new to Ruby, what's
the protocol for officially reporting bugs?  Do the language
maintainers use a Bugzilla somewhere?


Todd.