Signal SIGCHLD does not interrupt process blocked on read of pipe?

Signal SIGCHLD does not interrupt process blocked on read of pipe?

[Anthony Tuininga]

> I have a process which accepts requests from an Oracle database and
> passes them off to a process via Oracle's "pipe" mechanism. This
> process passes the information to another process which manages the
> requests and processes them. What is happening is that the second
> process spawns a process to handle the request and then goes back to
> reading the pipe. The spawned process completes and becomes <defunct>
> in the process listing but the SIGCHLD handler does not get triggered!
> A subsequent call (which causes the read on the pipe to terminate)
> causes the SIGCHLD handler to trigger and then does exactly the same
> thing!! This is really frustrating. Does anyone have any idea as to
> what is going on?
> 
> This is Windows NT 4.0 Workstation SP3 with cygwin32 beta 18 with the
> coolview patches by Sergey (latest version which I got today).
> 
> Thanks in advance for any help/suggestions,
> Anthony Tuininga
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Signal SIGCHLD does not interrupt process blocked on read of pipe?

[Tim Newsham]

> 
> I have a process which accepts requests from an Oracle database and
> passes them off to a process via Oracle's "pipe" mechanism. This
> process passes the information to another process which manages the
> requests and processes them. What is happening is that the second
> process spawns a process to handle the request and then goes back to
> reading the pipe. The spawned process completes and becomes <defunct>
> in the process listing but the SIGCHLD handler does not get triggered!
> A subsequent call (which causes the read on the pipe to terminate)
> causes the SIGCHLD handler to trigger and then does exactly the same
> thing!! This is really frustrating. Does anyone have any idea as to
> what is going on?

Signals do not interrupt blocking operations on pipes and sockets
in cygwin (there may be other blocking calls that do not yield
to signals as well).  This is because cygwin does a blocking call
into NT and gives up control of the thread until the call returns.
The cygwin signal mechanism causes the thread to stop, fiddles
with its stack, and then resumes the thread.  This means the signal
doesn't get delivered until the blocking call returns.

(Signal stuff is gonna change soon (or has already?) but I assume
the blocking behavior will remain the same).

As a work around you can use sockets instead of pipes, and make
sure to use only non-blocking socket calls (select() gets along
fine with signals).  You can patch your cygwin.dll to only
do non-blocking socket calls if you can't or don't want to patch
all of your sources. 

> Anthony Tuininga

                                          Tim N.

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Signal SIGCHLD does not interrupt process blocked on read of pipe?

[Anthony Tuininga]

I have a process which accepts requests from an Oracle database and
passes them off to a process via Oracle's "pipe" mechanism. This
process passes the information to another process which manages the
requests and processes them. What is happening is that the second
process spawns a process to handle the request and then goes back to
reading the pipe. The spawned process completes and becomes <defunct>
in the process listing but the SIGCHLD handler does not get triggered!
A subsequent call (which causes the read on the pipe to terminate)
causes the SIGCHLD handler to trigger and then does exactly the same
thing!! This is really frustrating. Does anyone have any idea as to
what is going on?

This is Windows NT 4.0 Workstation SP3 with cygwin32 beta 18 with the
coolview patches by Sergey (latest version which I got today).

Thanks in advance for any help/suggestions,
Anthony Tuininga

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".