Re: socket/signal problem tracked down - comments?

[cgf at cygnus dot com (Christopher G. Faylor)]

In article <m0yXJ0K-0011BMC.cygnus.gnu-win32@malasada.lava.net>,
Tim Newsham <newsham@lava.net> wrote:
>As for immediate fix for the connect() problem -- what is the preferred
>way to block signals while I'm in cygwin winsup code?  Should I do
>normal sigset operations to set the mask, or is there a simpler mechanism
>such as grabbing a semaphore or setting a flag?

block_sig_dispatch() will block signals from being acted on.
allow_sig_dispatch() will turn on signals and act on any signals that
have been queued.
-- 
cgf@cygnus.com             "Everything has a boolean value, if you stand
http://www.cygnus.com/      far enough away from it."  -- Galena Alyson Canada
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".