From: Laurent Julliard <laurent@...>
Date: 2002-10-19T05:05:17+09:00
Subject: Re: Is the debugger broken?

NAKAMURA, Hiroshi wrote:

> 
>>There are also problems with loops.
> 
> 
> Yes it has a limitation about tracing ruby's block
> (especially, one-line block).  Would you please post an
> example which causes loops problem?

Actually, any one line loop makes the debugger enter in a endless 
loop. try a simple thing like:

1 while true
2   i=1
3 done

And go through it with [n]ext.

This is a problem I have long observed while working on the FreeRIDE 
debugger. If my memory is correct the problem is that the tracer 
always stays on line 2 and there is some test in the trace_func 
function of the debugger forcing another step when we stay on the same 
line which of course causes an endless loop.

One way this can be fixed is that the tracer should really go through 
the while statement for each loop. However it will not solve the 
problem for code like:

i=0
while ((i=i.next) < 1000)
done

In this case the debugger go trough the 1000 iterations without stopping

Hope this helps. I think that if we could find a way to fix the one 
line loop that would be great because one-line loop are quite frequent.

Laurent