Any ideas? (Was: Signal handling)
Thu Apr 3 23:05:00 GMT 1997
In brief, signal handling in cygwin.dll does the following:
signal arrived (in separate signal processing thread);
if(signal masked or ignored)
if(signal handler == SIG_DFL)
suspend main thread;
save IP of main thread;
set main thread IP to signal handler address;
resume main thread;
exit signal thread;
when signal handler exits, restore original IP;
This scheme has one misfeature - signal handler will not start immediately
if main thread is in a blocking Win32 syscall (WaitForMultipleObjects(),
ReadConsoleInput() etc), but when this syscall terminates. This misfeature
brokes signal semantic. We can't start signal handler in a context of
signal processing thread, because this handler may never return (longjmp()
from within signal handler is allowed). Any ideas are welcome...
Looking for a job.
For help on using this list, send a message to
"firstname.lastname@example.org" with one line of text: "help".
More information about the Cygwin