On Jun 3, 2009, at 7:29 AM, Derick Eddington wrote:
The new debugger just helped me track down a bug in a deep stack of
frames which would have taken me a long time to narrow down the
control
path of without it. And the tail-call tracking is awesome. Thanks!
Glad it helps!
My only real problem with the debugger right now is its speed.
Depending on the program, it might take far more time to run
it in debug mode to reach the error than it would if you just
stare at the code and debug it the old-fashion way.
Running ikarus in non-debug mode should still provide some
information that it's currently not provided. You might lose
all tail-call information, and all parameter information, but
you should still be able to see the call frames, their source
positions, and the contents of these frames (i.e., the free
variables in each continuation). This is what I mean when I
say that we need an inspector in addition to the debugger.
Aziz,,,
