Andrew Stewart wrote:
> On Thursday, 5 May 2016 10:25:19 UTC+1, Andrew Stewart wrote:
> > >> When I edit a file my job runs. When I trigger a second run, Vim
> > >> always crashes with a segfault:
> > >>
> > >> Vim: Caught deadly signal SEGV
> > >> Vim: Finished.
> > >> Segmentation fault: 11
>
> I've just realised that every time a job runs, a new process is
> spawned as a child of vim's process, and they're all in the zombie
> state. They only disappear once I quit Vim or it crashes.
This must be a Mac specific problem, it doesn't call waitpid() to get
the status of the child. You can try using Vim as it's build on Unix,
should also work on Mac in a terminal.
--
"I love deadlines. I especially like the whooshing sound they
make as they go flying by."
-- Douglas Adams
/// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
