Vim: caught deadly signal SIGV #89

Closed
HendrikRoth opened this Issue May 17, 2012 · 4 comments

Comments

Projects
None yet
5 participants
@HendrikRoth

Typing ruby code, vim crashes after typing "." and then a character.

Vim version: VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 8 2012 15:05:17)
SPF13-vim (cloned an hour ago)

Example:
self.u --> crash (just wanted to type self.user_type)

@taxilian

This comment has been minimized.

Show comment
Hide comment
@taxilian

taxilian Sep 29, 2012

Contributor

This really sounds like some kind of problem with your vim installation; I can't reproduce this, and you haven't provided any information that would help us guess what might be causing the issue.

I'd try reinstalling (or rebuilding) vim and make sure you do so with ruby support. If you can use prebuilt binaries from a reliable source that'd be even better. The other thing to try is to disable the ruby-specific bundles (then run BundleClean!) and see if you can narrow down what specifically is causing the crash. it's likely something semi-specific to your system, but without more information we're just guessing.

Contributor

taxilian commented Sep 29, 2012

This really sounds like some kind of problem with your vim installation; I can't reproduce this, and you haven't provided any information that would help us guess what might be causing the issue.

I'd try reinstalling (or rebuilding) vim and make sure you do so with ruby support. If you can use prebuilt binaries from a reliable source that'd be even better. The other thing to try is to disable the ruby-specific bundles (then run BundleClean!) and see if you can narrow down what specifically is causing the crash. it's likely something semi-specific to your system, but without more information we're just guessing.

@wwalker

This comment has been minimized.

Show comment
Hide comment
@wwalker

wwalker Nov 27, 2012

henn1nk, I had a similar problem today. Then I ran "strace vim 2> /tmp/vim.strace" and recreated the failure. In my case I found that the ruby vim was linked against had been replaced, but whatever the problem is strace will probably narrow it down.

wwalker commented Nov 27, 2012

henn1nk, I had a similar problem today. Then I ran "strace vim 2> /tmp/vim.strace" and recreated the failure. In my case I found that the ruby vim was linked against had been replaced, but whatever the problem is strace will probably narrow it down.

@jrobeson

This comment has been minimized.

Show comment
Hide comment
@jrobeson

jrobeson Feb 2, 2014

Collaborator

@henn1nk : is this fixed for you now? if so, can you close it?

Collaborator

jrobeson commented Feb 2, 2014

@henn1nk : is this fixed for you now? if so, can you close it?

@jrobeson

This comment has been minimized.

Show comment
Hide comment
@jrobeson

jrobeson Jun 22, 2014

Collaborator

@spf13 : you can close this it seems. no response for awhile

Collaborator

jrobeson commented Jun 22, 2014

@spf13 : you can close this it seems. no response for awhile

@spf13 spf13 closed this Jun 30, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment