It seems to me that the debugger in 1.8.0preview4 always acts as if I’ve
used the ‘s’ command. That is, it stops on every line and enters every
file even if I’ve defined a breakpoint and issued the ‘c’ command.
Anybody else noticed this behavior?
It seems to me that the debugger in 1.8.0preview4 always acts as if I’ve
used the ‘s’ command. That is, it stops on every line and enters every
file even if I’ve defined a breakpoint and issued the ‘c’ command.
Anybody else noticed this behavior?
Hi,
From: “Tim Hunter” cyclists@nc.rr.com
Sent: Wednesday, July 30, 2003 11:21 AM
It seems to me that the debugger in 1.8.0preview4 always acts as if I’ve
used the ‘s’ command. That is, it stops on every line and enters every
file even if I’ve defined a breakpoint and issued the ‘c’ command.Anybody else noticed this behavior?
Though I don’t remember such a problem with preview4 or the
like CVS version, I could slip it.
I fixed 2 glitches about breakpoint handling at preview5.
Do you still have the same problem on preview5?
// NaHi
Tim Hunter wrote:
It seems to me that the debugger in 1.8.0preview4 always acts as if I’ve
used the ‘s’ command. That is, it stops on every line and enters every
file even if I’ve defined a breakpoint and issued the ‘c’ command.Anybody else noticed this behavior?
Yeup. Matz fixed it in p5. http://ruby-talk.org/76914
–
Chris
http://clabs.org/blogki