The following will fix #1155.


[cause of problem]

This problem may occur on some *nix environment.

Calling job_stop immediately after job_start, child process may receive signal
before reset_signals().
Therefore deadly-signals (except SIGKILL) are trapped by deathtrap() and so
can't terminate child process. Child remains as vim process image.

[solution proposal]

* Blocking deadly-signals by sigprocmask() before fork();
parent process (or fork-error) unblocks them promptly, and child process
does after reset_signals().

We need check sigprocmask availablity.

Thank you.
- Ozaki Kiichi

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.

Raspunde prin e-mail lui