You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #1837: Lazy-Initialization Refactoring Causing

Kind bug
Product Command-T
When Created , updated
Status closed
Reporter anonymous
Tags no tags

Description

The new refactoring of loading Command T is causing the error "Vim: Caught deadly signal SEGV" for MacVim 7.3 (system details below) and MacVim crashes. I recompiled the C, in case there was some kind of incompatible change, but I continue to get this error. The Command T panel appears correctly, and works with the first character I type. Typing a second character causes MacVim to crash and output the following to the Terminal from which I launched MacVim with mvim ..

$ Vim: Caught deadly signal SEGV Vim: Finished. 142H22;3M 153H22;4M$2;3M 215H

I reverted to the commit before that [1] and run rake make and Command T returns to functioning correctly.

System details:

  • Mac OS X 10.6.8
  • RVM installed, but rake make run after rvm use system to build with system Ruby
  • Stock MacVim 7.3 binary downloaded from Google Code page
  • Loading Command T through Pathogen

[1]: https://github.com/wincent/Command-T/commit/cee619ac6e906d1c6bfc3052f01ccaa6ac1d4b3c

Comments

  1. Greg Hurrell

    I think I might revert those commits, pending further investigation.

  2. Greg Hurrell

    Ok, reverted for now, and the lazy-initialization stuff is now on a topic branch. Can't really see anything in the topic branch that could cause a seg fault, but as lots of people track HEAD of master via Pathogen or similar, I prefer to be conservative and rollback until I'm sure the code doesn't have any negative side-effects.

  3. anonymous

    If there's any information I can provide to track down the cause of the crash, let me know. It was happening consistently with the latest changes before you reverted them and went away when I rolled back to a prior commit.

  4. anonymous

    I just updated to MacVim 7.3 (58) and I am getting this seg fault when starting mvim. The window never even appears, a message is just output "Vim: Caught deadly signal SEGV". If I remove the command-t plugin, the crash goes away. This continues to occur even after reverting the lazy initialization commits.

  5. Greg Hurrell

    Perhaps you are building it with the wrong version of Ruby. Are you are rvm user, by any chance? If so, you need to build with the system Ruby, which is what MacVim links against.

  6. anonymous

    Sorry, my mistake. I knew that you had to use the system Ruby, but evidently I wasn't. I just tried it again and its working great. Thanks!

  7. Greg Hurrell

    Closing as the lazy-initialization was reverted and later replaced by use of Vim's autoload mechanism.

  8. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu