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

Bug #2106: Another Command-T segfault thread..

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

Description

Hi there, thanks for making this plugin available

I'd like to report "yet-another" segfault bug. I realize that most of the times this happens because a mismatch between Ruby versions, however this does not seem to be the case with me.

I am using Homebrew on mac and I use the homebrew's Ruby 2.0.0 version to compile both vim 7.4 and to make Command-T.

which ruby returns

/usr/local/bin/ruby

ruby -v returns

ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.4.0]

inside vim running ':ruby puts RUBY_VERSION' yields '2.0.0'

My command-t plugin directory shows revision 8866bbc, from 4 months ago.

It works fine but after some minutes it invariably throws the infamous: "Vim: Caught deadly signal SEGV"

I don't know how to reproduce it as it seems a bit erratic, but it always happens at some point.

I don't know exactly how to obtain a stack trace, but I can certainly do so if instructed.

Hope this helps.

Comments

  1. Greg Hurrell

    Haven't seen this one myself. I'm also using Homebrew-installed Vim, but mine is using the system Ruby (1.8.7). I do know that colleagues at my work are using Command-T with Vim 7.4 with Ruby 2.0.0, albeit on a different OS (CentOS).

    (I don't really feel any urgency to have Vim use the latest and greatest Ruby, so I haven't bothered updating my local dev environment yet.)

  2. Greg Hurrell

    Closing due to lack of activity.

  3. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu