Bug #2080: :CommandT Crashs Vim with log "Trace/BPT trap: 5"

$ ruby -v
ruby 1.9.3p392 (2013-02-22 revision 39386) [x86_64-darwin12.2.0]
$ vim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jun 20 2012 13:16:02)

Vim: Caught deadly signal TRAP
Vim: Finished.
Trace/BPT trap: 5

Comments

1. Greg Hurrell 2013-04-16T15:39:07Z

   It's probably miscompiled; in order to work, both Vim and Command-T must be linked against the exact same version of Ruby. See other similar tickets in the issue tracker and the forums, where compiling against the right version of Ruby invariably solves the problem.

2. Greg Hurrell 2013-04-16T15:49:49Z

   Product changed:

   • From: none
   • To: Command-T

3. Greg Hurrell 2013-04-16T15:50:04Z

   Status changed:

   • From: new
   • To: open

4. anonymous 2013-09-24T16:05:46Z

   So I had the same issue.

   To be sure I got this right, I did

   $ rvm use 1.8.7

   and then removed and re-installed vim via homebrew.

   $ otool -L $(which vim) | grep ruby
   /Users/[username]/.rvm/rubies/ruby-1.8.7-p374/lib/libruby.dylib (compatibility version 1.8.0, current version 1.8.7)
   $ ruby --version
   ruby 1.8.7 (2013-06-27 patchlevel 374) [i686-darwin11.4.2]
   $ ruby extconf.rb                                                                                                            
   checking for ruby.h... yes
   creating Makefile
   $ make
   cc -dynamic -bundle -undefined suppress -flat_namespace -o ext.bundle ext.o match.o matcher.o -L. -L/Users/[username]/.rvm/rubies/ruby-1.8.7-p374/lib -L. -L/usr/local/opt/libyaml/lib -L/usr/local/opt/readline/lib -L/usr/local/opt/libksba/lib -L/usr/local/opt/openssl098/lib    -lruby  -ldl -lobjc
   $ vim
   Vim: Caught deadly signal TRAP
   Vim: Finished.
   Trace/BPT trap: 5

   From here everything looked exactly right for me, but I didn't realize that make didn't do anything because the plugin was already compiled. I removed the plugin and let neobundle re-install it for me, after which I tried again. Now it works fine.

   Probably a make clean would also have solved the issue.

5. Greg Hurrell 2013-09-24T17:40:36Z

   Status changed:

   • From: open
   • To: closed

6. anonymous 2014-07-04T10:32:29Z

   $ ruby -v
   ruby 2.0.0p353 (2013-11-22 revision 43784) [x86_64-darwin13.0.0]

   it aslo broken !

Add a comment

Comments are now closed for this issue.