Ohmigod! That would have never occurred to me in a million years.
I guess that's why I'm in QA.
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.
I'm not sure
exactly how you'd precisely define what an executable line
is.
Well, in some cases it may be difficult. In many cases,
though, it's quite simple. A blank line is not executable.
A comment line is not executable, either.
Todd.