[ruby-talk:00482] Re: Modified debug.rb

Oops, I sent the message too soon.

But in the debugger,  notice the following:
o   the source listing tracks the current frame position
o   a simple arrow is shows the current position
o   evaluation of expressions is done in the current frame.

The only missing element is the ability to skip over the statement
that caused the exception.  Currently, c(ontinue) will simply return
from the debugger while the exception is still there, causing a
premature exit:

>> ...
>> (rdb:-) list
>>         9 foo(10)
>> -->    10 bar('a')
>>        11 bar(122)
>> (rdb:-) c
>> debug-test.rb:2:in `foo': undefined method `/' for "a" (NameError)
>>         from debug-test.rb:6:in `bar'
>>         from debug-test.rb:10
>> ...


Is there a way to skip (in this example) the exception from "bar('a')"
and still execute "bar(122)"?

Cheers,
Michael

P.S.  Matz, perhaps you want to merge my modifications to debug.rb
with nahi's?  This may not be pretty, though..