On 15 August 2010 19:58, Nikola Knezevic wrote: >> > I debugged the problem and found that it is caused by calling setsid() >> > when forking but have no idea why this is [2]. It is called from >> > macos_fork() inside src/os_macosx.m in case you feel like debugging >> > the issue. I'd appreciate the help -- I'm not getting anywhere with >> > it. > > I took a look at the code. I can't figure out why the problem occurs, > but I solved it by using double-fork(). This way, I ensure that MacVim > process becomes a child of init. Double fork()-ing is often used when > you want to make sure that the child doesn't inherit anything from the > parent. > > Here is the patch I used, let me know if it works for you: > <http://lpd.epfl.ch/knezevic/setsid.patch>
Thanks. I'll take a look at it but not before the 7.3 release...we've had some severe fork-related problems in the past so I don't dare to include this without some testing first. I don't at all understand these forking issues (indeed I don't understand why we can't just leave out the setsid() call since this also gets rid of the problem). Does double-forking have any obvious negative side effects? Björn -- You received this message from the "vim_mac" 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
