This is the mail archive of the cygwin 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: Signal handling in Win32 GUI programs


On Tue, Jan 13, 2009 at 7:29 AM, Andy Koppe wrote:
> Actually I still can't quite get signal handling in MinTTY to work right.
> SIGINT is fine, but SIGTERM, SIGHUP, and SIGKILL don't seem to get to
> sigwait(), instead still invoking the default handler, i.e. terminating
> MinTTY without SIGHUP being sent to the command inside it.

> Anything obvious missing?

Shouldn't pthread_sigmask be called for signal_thread as well?
>From the Linux manual page:
"In a multithreaded program, the signal should be blocked in all
threads to prevent the signal being delivered to a thread other than
the one calling sigwaitinfo() or sigtimedwait()). "
But maybe that doesn't apply to Cygwin.

Chris

--
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/


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