≡

wincent.dev

  • Products
  • Blog
  • Wiki
  • Issues
You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.
Home » Issues » Support ticket #1991

Support ticket #1991: Crashes Vim on Mountain Lion

Kind support ticket
Product Command-T
When Created 2012-07-25T16:47:31Z, updated 2014-03-22T20:39:36Z
Status closed
Reporter anonymous
Tags no tags

Description

Just upgraded my computer from Lion to Mountain Lion, and the Command-T plugin quit working. It will now crash vim, and output:

Vim: Caught deadly signal TRAP
Vim: Finished.
[1]    33282 trace trap  vi .vimrc

I've tried rebuilding macvim, and rebuilding command-t, but nothing seems to be working. Any suggestions as to what I should try?

Comments

  1. Greg Hurrell 2012-07-26T16:55:58Z

    You've already tried what I would suggest. I'm not on Mountain Lion yet, but will try upgrading this weekend. At that point I'll be able to see if I can repro and suggest/make a fix.

  2. Greg Hurrell 2012-07-26T16:56:04Z

    Status changed:

    • From: new
    • To: open
  3. Greg Hurrell 2012-07-28T07:06:25Z

    So I upgraded to Mountain Lion last night and I've had time to test out Command-T.

    I installed Xcode 4.4 and the command line tools package, then checked for a newer version of MacVim. The binary version that I previously had (snapshot 64) was already the latest, so I left it as-is.

    I then rebuilt Command-T, using the system Ruby, and it works fine in MacVim.

    Following that I tried command-line Vim, a 7.3 build that I made from source back in August. I didn't touch it or rebuild it, but confirmed that Command-T works with it.

    So everything seems to work. My best guess is that you might have RVM or rbenv in the way, which are somehow causing Vim/MacVim and Command-T to not be linked against the exact same version of Ruby. Is this the case?

  4. anonymous 2012-07-29T16:56:05Z

    I get the following error when i try to use \t:

    dyld: lazy symbol binding failed: Symbol not found: _rb_intern2
      Referenced from: /Users/khr128/.vim/bundle/command-t/ruby/command-t/ext.bundle
      Expected in: flat namespace
    
    dyld: Symbol not found: _rb_intern2
      Referenced from: /Users/khr128/.vim/bundle/command-t/ruby/command-t/ext.bundle
      Expected in: flat namespace
    
    Vim: Caught deadly signal TRAP
    Vim: Finished.

    My ruby version is managed by rbenv:

    command-t:126➫  ruby -v
    ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin12.0.0]

    My VIM version:

    :version
    VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jul 29 2012 09:48:32)
    MacOS X (unix) version
    Included patches: 1-390
    Compiled by khr128@DMITRIs-iMac.local
    Huge version with MacVim GUI.  Features included (+) or not (-):
    +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist
    +cmdline_info +comments +conceal +cryptv -cscope +cursorbind +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic +emacs_tags
    +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +float +folding -footer +fork() +fullscreen -gettext -hangul_input
     +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap -lua +menu +mksession
    +modify_fname +mouse +mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm +mouse_urxvt
    +multi_byte +multi_lang -mzscheme +netbeans_intg +odbeditor +path_extra +perl +persistent_undo +postscript +printer +profile
    +python -python3 +quickfix +reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff +startuptime +statusline -sun_workshop
    +syntax +tag_binary +tag_old_static -tag_any_white +tcl +terminfo +termresponse +textobjects +title +toolbar +transparency
    +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -X11
    -xfontset +xim -xsmp -xterm_clipboard -xterm_save
       system vimrc file: "$VIM/vimrc"
         user vimrc file: "$HOME/.vimrc"
          user exrc file: "$HOME/.exrc"
      system gvimrc file: "$VIM/gvimrc"
        user gvimrc file: "$HOME/.gvimrc"
        system menu file: "$VIMRUNTIME/menu.vim"
      fall-back for $VIM: "/Applications/MacVim.app/Contents/Resources/vim"
    Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe  -isystem /usr/local/include -DMA
    COS_X_UNIX -no-cpp-precomp  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1     -I/System/Library/Frameworks/Tcl.framework/Headers  -D_
    REENTRANT=1  -D_THREAD_SAFE=1  -D_DARWIN_C_SOURCE=1
    Linking: gcc   -L.   -L.       -L/usr/local/lib -o Vim -framework Cocoa -framework Carbon      -lncurses -liconv -framework Cocoa
     -fstack-protector -L/usr/local/lib  -L/System/Library/Perl/5.12/darwin-thread-multi-2level/CORE -lperl -lm -lutil -lc -framework Py
    thon  -F/System/Library/Frameworks -framework Tcl -framework CoreFoundation -framework Ruby

    I built VIM with home-brew.

  5. Greg Hurrell 2012-07-29T18:27:49Z

    It looks like when you build Vim using homebrew it links again the system Ruby. You'll need to build Command-T linking against the same Ruby.

  6. Greg Hurrell 2014-03-22T20:39:36Z

    Status changed:

    • From: open
    • To: closed
Add a comment

Comments are now closed for this issue.

  • contact
  • legal

Menu

  • Blog
  • Wiki
  • Issues
  • Snippets