Am Freitag, 5. Oktober 2012 10:06:43 UTC+2 schrieb Patrick Steinhardt: > Hi, > > > > I had similar problems with clang_complete and editing C source files. > > My solution has been to use a more up to date version of > > clang_complete, as the version from vimscripts is not really up to > > date at all. I am now using the Git version from [1], which fixed the > > segfault. > > > > Regards, > > Patrick > > > > > > [1] https://github.com/Rip-Rip/clang_complete > > > > On Thu, Oct 04, 2012 at 03:18:35PM -0700, thomasg wrote: > > > Hi everyone, > > > > > > I'm not really sure if this is a bug in Vim directly because I'm using > > > some extension scripts which directly trigger it; > > > however, as Vim is segfaulting I assume the bug is is only triggered > > > and not directly caused by the scripts. > > > > > > Environment: > > > - vim-7.3.646 > > > - clang_complete plugin > > > - c-support (c.vim) plugin > > > - Vundle "script manager" > > > > > > Scenario: > > > Vundle is active, above mentioned plugins are installed via vundle > > > (which works fine so far). > > > Opening a file ending on .c (which causes clang_complete and c-support > > > to kick in) results in a segfault: > > > Vim: Caught deadly signal SEGV > > > zsh: segmentation fault (core dumped) LANG=C vim test.c > > > > > > Workaround: > > > Disabling the option: g:clang_use_library makes the segfault go away, > > > which indicates that clang_complete is responsible for triggering the > > > bug. > > > > > > I do not seem to be able to attach the files (google groups as well as its > > mailinglist interface fails silently while appearing to be successful), so > > you can get the needed report files here: > > > [1] http://gstaedtner.net/bugs/vim_segfault00-bugreport.txt > > > [2] http://gstaedtner.net/bugs/vim_segfault00-gdb_backtrace.txt > > > > > > Please let me know if I can provide any more information, or in case I > > > should report the bug at the clang_complete bugtracker instead. > > > > > > Thanks in advance, > > > > > > -- > > > ~thomasg > > > > > > -- > > > 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
Thanks for the reply Patrick. In my case it actually is a too new version that causes this behavior which I tracked down via git bisect. This also indicates that vim might not be at fault (though I first thought it should not segfault due to a failing plugin), but indeed clang_completes fault. I guess this closes the matter here. For reference: I filed a bug at clang_completes tracker: https://github.com/Rip-Rip/clang_complete/issues/202 -- thomasg -- 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
