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

Bug #1767: Frequent Crashes on Mandriva Linux Cooker on x86-32 When Browsing Trunk of Test-Run

Kind bug
Product Command-T
When
Status closed
Reporter Shlomi Fish
Tags no tags

Description

Hi Wincent,

thanks for command-t.vim and other programs - command-t seems very cool from command-t-demo.mov . However, when I try to use it on the Test-Run project on Mandriva Linux Cooker (after compiling vim from hg / etc. afresh), I'm running into frequent crashes. I'm checking out:

Into /home/shlomif/progs/perl/cpan/Test/Test-Harness/trunk and then cd-ing into the trunk and invoking gvim there and trying to use command-t.vim (after successfully building it and running it):

Typing this crashes it:

\t
mtrbpl[Enter]
\t
trstr[Enter]
\tvbv
mbtro[Enter]
mbababa   # Quickly.

I'm on a P4-2.4GHz machine (x86-32) running Mandriva Linux Cooker and am getting this: 

shlomif:$trunk$ gvim
shlomif:$trunk$ /home/shlomif/.vim/ruby/command-t/finder.rb:40: [BUG] gc_sweep(): unknown data type 0x10(0xb57f2514)
ruby 1.8.7 (2010-12-23 patchlevel 330) [i586-linux]

Vim: Caught deadly signal ABRT
Vim: Finished.

Please look into it.

Regards,

-- Shlomi Fish

Comments

  1. Greg Hurrell

    I am pretty sure there are no crashing bugs in the code right now — believe me, it would make my day if you could surprise me by finding one and supplying a patch, but I honestly don't think there are any to find — so there are two possible causes for the crashes you're seeing:

    • one is that you might have compiled the plug-in with a different version of Ruby than the one you linked against when building Vim; the solution here is to carefully ensure that you use exactly the same version for both
    • the other is a general instability in Vim 7.3 with regard to Ruby; unfortunately this one is a little difficult to troubleshoot as it seems to only manifest itself on certain platforms and with certain combinations of Vim/Ruby — in the case the simplest workaround is to drop back to 7.2, although if you're a masochist you could decide to start digging down and trying to find out the cause of these GC crashes

    If you look through the issues on the issue tracker here, or the threads in the Command-T forums, you'll see posts on both of these types of issue with examples of how people were able to solve their problems. Ticket #1741 seems to be the most recent example of this, so I'm going to mark this one as closed seeing as it's a duplicate. If you have any further comments to add please add them there.

  2. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu