Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 3 Feb 2004 13:35:06 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Is there a translation from windows events to cygwin signals ? Message-ID: <20040203183506.GC3696@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: <20040203171711.GC14675@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin@cygwin.com On Tue, Feb 03, 2004 at 12:50:19PM -0500, Igor Pechtchanski wrote: >On Tue, 3 Feb 2004, Christopher Faylor wrote: >>On Tue, Feb 03, 2004 at 10:54:40AM -0500, Igor Pechtchanski wrote: >>>Cygwin signals use Windows events under the covers, but there's more to >>>Cygwin signals than just Windows events. There's no one-to-one >>>mapping. Use "kill". >> >>Actually, no, they don't really use windows events. Not since 1.5.6. > >Fair enough (just goes to show how out-of-date my CVS checkout is). >:-) To the OP: the authoritative document on this used to be the >"how-signals-work.txt" file in winsup/cygwin, which is currently out of >date. Watch it for updates, but until then, the code is your best >guide. To get the source from CVS, see . And, just to be clear, the third line in how-signals-work.txt is already "[this information is currently out-of-date]" so there should be no confusion for anyone who thinks this is the definitive source for how signals work in cygwin. cgf -- 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/