Mail Archives: cygwin/2004/10/07/12:50:34
On Thu, Oct 07, 2004 at 11:30:42AM -0500, Brian Ford wrote:
>On Wed, 6 Oct 2004, Christopher Faylor wrote:
>
>> On Wed, Oct 06, 2004 at 12:24:48PM -0400, Remy Gauthier wrote:
>> >We have noticed (on V1.5.10-1 and V1.5.11-1) that after a call to
>> >system(), the handlers were not being called after the child process
>> >stopped. This program has this behaviour (removing the call to
>> >system() will restore correct SIGCHLD handling):
>[snip; from Linux system(3)]
>> During execution of the command, SIGCHLD will be blocked, and SIGINT and
>> SIGQUIT will be ignored.
>
>Um..., I think you missed the point here cgf as this didn't answer the
>question. The key word above is "During". He was reporting that it
>was still in effect "after", and he identified the cause here:
Shame on me for not reading the original message more thoroughly and
ass*u*me ing that it was a standard complaint about documented system()
behavior.
The fix is trivial and checked in. I apologize for my incorrect answer
and for any confusion I caused.
This will be in the next snapshot, which I've just kicked off now:
http://cygwin.com/snapshots/
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -