Aron Griffis wrote:
> On Saturday, July 8, 2017 at 4:38:36 PM UTC-4, Bram Moolenaar wrote:
> > Patch 8.0.0702
> > Problem: An error in a timer can make Vim unusable.
> > Solution: Don't set the error flag or exception from a timer. Stop a
> > timer
> > if it causes an error 3 out of 3 times. Discard an exception
> > caused inside a timer.
> > Files: src/ex_cmds2.c, src/structs.h, src/testdir/test_timers.vim,
> > runtime/doc/eval.txt
>
> This patch is causing segfaults for me. I've built with and without it to
> verify.
>
> I have a timer to check a couple files and update my color scheme when they
> change. I haven't tried to narrow down any specific lines yet, but when
> TryTheme actually triggers then vim segfaults immediately. Maybe because of
> the try/catch?
>
> Here's the code from my vimrc:
[..]
I haven't managed to reproduce it. Can you run Vim in a debugger and
see the call stack?
--
hundred-and-one symptoms of being an internet addict:
133. You communicate with people on other continents more than you
do with your own neighbors.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" 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
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
