> On 9 May 2016, at 4:24 pm, Bram Moolenaar <[email protected]> wrote:
> 
> Andrew Stewart wrote:
> 
>>> On 4 May 2016, at 8:49 pm, Bram Moolenaar <[email protected]> wrote:
>>> 
>>> boss wrote:
>>>> I upgraded from Vim 7.4.1795 to 7.4.1816 and found DETACH was no longer 
>>>> sent to the `out_cb` handler to demarcate the end of my job's output on 
>>>> stdout.
>>>> 
>>>> So I added a `close_cb` handler which does what my `out_cb` handler used 
>>>> to do on receiving DETACH: it gathers together all the preceding job 
>>>> output and then processes it.
>>>> 
>>>> When I edit a file my job runs.  When I trigger a second run, Vim
>>>> always crashes with a segfault:
>>>> 
>>>> Vim: Caught deadly signal SEGV
>>>> Vim: Finished.
>>>> Segmentation fault: 11
>>>> 
>>>> Here's my code:
>>> 
>>> Thanks for the description.  I'll try to reproduce.
>> 
>> In case you can't reproduce with my code snippets, the actual code is here:
>> 
>> https://github.com/airblade/vim-gitgutter/tree/async
>> 
>> i.e. the "async" branch of the repo.
>> 
>> The callbacks are in this file:
>> 
>> https://github.com/airblade/vim-gitgutter/blob/async/autoload/gitgutter/async.vim
>> 
>> To reproduce:
>> 
>> 1. Install the plugin from the repo's async branch.
>> 2. Edit a file from a git repo and make some changes.
>> 3. You should see diff signs in the sign column.  They show up after 
>> &updatetime and/or when you write the buffer.
>> 4. After one or two modifications Vim will segfault (it does for me).
>> 
>> To turn on logging use `let g:gitgutter_log = 1`.  This will write a 
>> channel.log and a gitgutter.log to the plugin's directory.
>> 
>> Thanks for investigating all this!
> 
> Patch 7.4.1826 should fix this.  Let me know if you still see a problem.

It does fix it, and it also fixes my redraw-not-working problem.  In fact I 
don't need the redraw at all.

Everything's working perfectly for me now.

Thank you very much!

-- 
-- 
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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui