Excerpts from talek's message of Sun Jan 16 14:49:01 +0100 2011:
> Hi Dominique,
>
> Thanks a lot for this patch. Indeed, it solves the unexpectedly exit
> of vim when ruby is used and VTALRM signal is received. I've just made
> a few tests and it's working great. I believe VTALRM signal has to do
> with the way ruby implements its green threads. The crash looks like
> "[Bug #2103] rev23993 causes Virtual Timer Expired when
> forking" (http://www.ruby-forum.com/topic/195414) but according to
> ruby-enterprise guys the bug fix is included in their last ruby
> enterprise package (http://blog.phusion.nl/2009/10/26/ruby-enterprise-
> edition-1-8-7-2009-10-released/). Now, the big question is: are there
> any chances this patch to be included into the official vim trunk? How
> a patch becomes an official one?
>
> -- talek
Hi talek, Dominique,
The patch contained:
-#ifdef SIGVTALRM
+#if defined(SIGVTALRM) && !defined(FEAT_RUBY)
+ /* Ruby uses SIGVTALARM which makes Vim exit. */
{SIGVTALRM, "VTALRM", TRUE},
#endif
My sources contain this: (note the FALSE!)
#ifdef SIGALRM
{SIGALRM, "ALRM", FALSE}, /* Perl's alarm() can trigger it */
#endif
My source version: ftp://ftp.vim.org/pub/vim/unix/vim-7.3.tar.bz2
So maybe this FALSE is the upstream fix? Which version have you both
been using?
I checked both: amd64 and i686 versions and can't reproduce the issue.
Marc Weber
--
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
