> First step is to try without Ruby. Most probably it is Ruby that > causes the problem.
Yes, I also suspect ruby is the problem. If I'd be able to reproduce the bug using just ruby then I can report it directly to the ruby community. Is it something special in the way vim makes calls and inter-connects with the ruby interpreter? Using valgrind I get: ==8072== Invalid write of size 4 ==8072== at 0x823E333: ??? (in /usr/local/bin/vim) ==8072== by 0x823E967: rb_thread_create (in /usr/local/bin/vim) ==8072== by 0x733A668: pty_getpty (pty.c:442) ==8072== by 0x822F884: ??? (in /usr/local/bin/vim) ==8072== by 0x823794C: ??? (in /usr/local/bin/vim) ==8072== by 0x8237AE8: ??? (in /usr/local/bin/vim) ==8072== by 0x8241CF8: ??? (in /usr/local/bin/vim) ==8072== by 0x82357B9: ??? (in /usr/local/bin/vim) ==8072== by 0x82356D9: ??? (in /usr/local/bin/vim) ==8072== by 0x8244DC9: ??? (in /usr/local/bin/vim) ==8072== by 0x8245692: rb_eval_string (in /usr/local/bin/vim) ==8072== by 0x82312E8: rb_protect (in /usr/local/bin/vim) ==8072== Address 0xbe9f67b8 is just below the stack ptr. To suppress, use: --workaround-gcc296-bugs=yes ==8072== Vim: Caught deadly signal VTALRM Vim: Finished. ==8072== ==8072== HEAP SUMMARY: ==8072== in use at exit: 2,173,158 bytes in 30,633 blocks ==8072== total heap usage: 166,041 allocs, 135,408 frees, 11,591,377 bytes allocated ==8072== ==8072== LEAK SUMMARY: ==8072== definitely lost: 10,510 bytes in 131 blocks ==8072== indirectly lost: 15,195 bytes in 760 blocks ==8072== possibly lost: 1,113,102 bytes in 14,355 blocks ==8072== still reachable: 1,034,351 bytes in 15,387 blocks ==8072== suppressed: 0 bytes in 0 blocks ==8072== Rerun with --leak-check=full to see details of leaked memory ==8072== ==8072== For counts of detected and suppressed errors, rerun with: -v ==8072== ERROR SUMMARY: 265 errors from 2 contexts (suppressed: 226 from 12) But, I have very little experience with valgrind, gdb and other such tools therefore I don't know if the above reveals anything useful. -- talek -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
