This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch]: Setting the winpid in pinfo


On Fri, Sep 10, 2004 at 11:13:37PM -0400, Pierre A. Humblet wrote:
>>If the child process has not become fully awake yet it should just exit now.
>
>Not if it is destined to ignore ^C. The group leader will wait until the 
>[grand]child has grown up and its sendsig is != NULL, and then send the
>signal.
>The child will then handle it properly.
>
>The motivation for looking at this was
><http://cygwin.com/ml/cygwin/2004-07/msg01120.html>, as well as personal
>observations. I have run thousands of tests and eveything has gone well.

I think I would be more comfortable with deferring signals around a fork.
It seems like that is the right way to handle this.  Then the parent would
not disappear mysteriously and there would be no need to have the child
wait for the parent.  Your exceptions.cc change would still be required,
however.

There currently is no way to stop signals from being delivered but it
is trivial to add something.

Wouldn't that solve this problem?

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]