Xavier de Gaye <[email protected]>:
> On Fri, Nov 18, 2011 at 6:39 AM, Jan Larres wrote:
>> I just spent some time hunting done a segfault that was cropping up recently
>> for me, and I have narrowed it down to some python threading that the
>> clang_complete plugin is doing. I have attached a minimal vimrc that is
>> needed
>> to make the bug appear, the two stripped-down plugin files (just put them
>> into
>> ~/.vim/plugin), a gdb backtrace log and my version information (it's the
>> newest
>> one with all patches applied).
>
>
> The problem is that the python interface in Vim is not thread safe.
That's what I was worried about. I assume there's no easy way to fix
this then, other than using a higher sleep() value. But that just seems
wrong, especially since it can randomly lead to segfaults :(
Jan
--
-[ OpenPGP key ID: 00A0FD5F ]-
I do not fear death. I had been dead for billions and billions of years
before I was born, and had not suffered the slightest inconvenience from it.
-- Mark Twain
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
