[slim-vim] More details on the socket crash bug
Larry Clapp
larry at theclapp.org
Fri Jun 16 07:41:54 CDT 2006
On Thu, Jun 15, 2006 at 10:50:36PM -0700, Brad Beveridge wrote:
> My thoughts from tonight's debugging:
> Although Vim is only single threaded, almost any chunk of Vim code
> can and will call RealWaitForChar, which is where our networking
> callbacks happen. Code that runs in ECL can and will end up calling
> RealWaitForChar, which may trigger callbacks to ECL. I still think
> this is our problem, and I have caught it in this state before.
I tend to agree, but I find the below question interesting, too.
> However, I've tried placing crude mutexes around bits and pieces, I
> still see the problem and RealWaitForChar is not appearing more than
> once in my call stack.
> Random thought - has anybody checked to see if garbage collection is
> working properly?
Perhaps GC works all too well, and our callback function moves, but
the C code has no notion of that. :(
I've tried mutexes, too, but only in the Lisp code. I should try it
in the C code.
-- L
More information about the slim-vim
mailing list