Re: debug performance problem

[David Ponce]

Hi Richard,

> I have one other idea for speeding it up, though.  It could be
> possible to save the backtrace text from the previous debugger
> invocation, and that way only the part that has changed needs to be
> rescanned.
>
> Does this make it adequately fast?

I try your new code but now the debugger don't work any more.  It seems
to just move the cursor to next word in the debugger buffer when I hit
'd'.  Any idea?

Here are the messages I saw after respectively typing 'c', 'd', 'j' and
'q':

Entering debugger...
sym nil, file nil
Continuing.
sym nil, file nil
Proceeding, will debug on next eval or call.
sym a, file nil
Continuing through this frame
sym nil, file nil
Back to top level.


Thanks!
David
____________________________________________________________
Faites un voeu et puis Voila ! www.voila.fr
Avec Voila Mail, consultez vos e-mails sur votre mobile Wap.