[slim-vim] ECL + Vim, debugging issues

[Brad Beveridge]

On 26/06/06, Larry Clapp <larry at theclapp.org> wrote:
> On Mon, Jun 26, 2006 at 11:45:37AM -0700, Brad Beveridge wrote:
> > I have occasionally run into errors that crash my Vim out to an ECL
> > REPL.  Normally this would be fine, but Vim messes with the ususal
> > console behaviour, so you end up with a console that will accept
> > keystrokes, but won't echo them.
> >
> > I usually run into this problem when my Slim-vim code references a
> > symbol that doesn't exist, or calls a function that doesn't exist.
> > I occasionally mess up and rename stuff, but not in all the right
> > places :)  I haven't looked into this at all, but it doesn't seem
> > reasonable to break Vim quite so badly.  This isn't bothering me
> > enough to fix myself (yet!), but I thought I'd document it.  Maybe
> > some kind soul will look into it :)
> >
> > I suspect something like ":ecl (blah)", where BLAH doesn't exist
> > will probably reproduce this.
>
>   :ecl (blah)
>
> gets me "ERROR: The function BLAH is undefined."
>
>   :ecl (print blah)
>
> gets me "ERROR: The variable BLAH is unbound."
>
>   COMMON-LISP-USER> (defun foo () (foo))
>   FOO
>   COMMON-LISP-USER> (foo)
>   Frame stack overflow.
>
>   COMMON-LISP-USER>
>
> I've crashed my Vim back to the terminal, too, but not lately (i.e.
> not during any of the development I did this weekend).  If you can
> reproduce it, please document it here.

Ok, guess I shouldn't have done it from memory :)  But given your
results, I'll bet that my crashes have happened in the listener
callback.  Quite a bit of ECL code gets run during a callback now,
which is probably why I didn't immediately realise the problem.

Cheers
Brad