From: khan@xraylith.wisc.edu (Mumit Khan) Subject: Re: Signal handling for cygwin.dll 4 Apr 1997 04:01:34 -0800 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <9704040645.AA26575.cygnus.gnu-win32@modi.xraylith.wisc.edu> Original-To: Sergey Okhapkin Original-Cc: gnu-win32@cygnus.com In-Reply-To: Your message of "Tue, 01 Apr 1997 16:09:43 +0400." <01BC3EB7.251A0210@gater.krystalbank.msk.ru> Original-Sender: owner-gnu-win32@cygnus.com Sergey Okhapkin writes: > Hi! > > This patch adds interprocess signals support with (almost :-) unix > semantics for cygwin.dll while running on Windows NT. The only supported > signal on Windows 95 is SIGKILL, because of Win32 API call > CreateRemoteThread() is not supported on W95, and I don't see any way to > implement signals without this call easy... This patch also includes my > "Ctrl-C in bash" patch. Any bug reports/improvements are welcome. To test > this patch I've used the following simple program: Hi Sergey, Thank you for these patches! The only thing I can add is the following trivial patchlet: *** newlib/libc/include/signal.h.~1 Thu Apr 3 23:31:59 1997 --- newlib/libc/include/signal.h Thu Apr 3 23:32:28 1997 *************** extern "C" { *** 6,9 **** --- 6,10 ---- #include "_ansi.h" + #include /* needed for pid_t */ #include Regards, Mumit -- khan@xraylith.wisc.edu http://www.xraylith.wisc.edu/~khan/ - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".