8000 SegFault collection with Fugitive · Issue #9 · sjl/splice.vim · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

SegFault collection with Fugitive #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
f0086 opened this issue Nov 23, 2012 · 3 comments
Open

SegFault collection with Fugitive #9

f0086 opened this issue Nov 23, 2012 · 3 comments

Comments

@f0086
Copy link
f0086 commented Nov 23, 2012

I got some ugly crashes when using splice with fugitive:

Occured randomly on changing to [c]ompare

Vim: Caught deadly signal SEGV
Vim: Finished.
/usr/lib/git-core/git-mergetool--lib: line 137: 17339 Segmentation fault      vim -f $BASE $LOCAL $REMOTE $MERGED -c 'SpliceInit'

Occured randomly on changing to [p]ath

*** glibc detected *** vim: malloc(): smallbin double linked list corrupted: 0x00000000026dadb0 ***

$ vim --version | head -4
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 23 2012 18:42:18)
Included patches: 1-712
Compiled by ArchLinux
Big version with GTK2 GUI.  Features included (+) or not (-):

$ git --version
git version 1.8.0

$ pacman -Q glibc
glibc 2.16.0-5

How can I provide better logs/stacktraces?
igrekster pushed a commit to igrekster/splice.vim that referenced this issue Feb 5, 2013
Fixes issue sjl#9.
ae226ca
@majutsushi
Copy link

That indeed seems to fix the issue for me. Could this be merged, please?

@lfilho
Copy link
lfilho commented Jun 2, 2013

It seems like @sjl already put these changes in ( #12 ). Although not via a PR merge.

@sjl can you confirm, then, tha 86CF t Splice works well with fugitive? The readme still says it doesn't...

Thanks a lot!! AWESOME plugin!

@majutsushi
Copy link

Huh, how did I miss that? It haven't been able to reproduce the segfault after adding this fix manually, so I guess it's really fixed now. Except that it's probably still a bug in Vim, though.

@errael errael mentioned this issue Aug 22, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@f0086 @lfilho @majutsushi
0