X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 6 May 2010 10:38:37 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Signal support under Cygwin Message-ID: <20100506143837.GA16107@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20100505142321 DOT GA21280 AT ednor DOT casa DOT cgf DOT cx> <4BE204FD DOT 5080500 AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BE204FD.5080500@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Thu, May 06, 2010 at 12:53:33AM +0100, Dave Korn wrote: >On 05/05/2010 23:57, Nicholas Sherlock wrote: >> On 6/05/2010 2:23 a.m., Christopher Faylor wrote: >>> On Thu, May 06, 2010 at 02:20:54AM +1200, Nicholas Sherlock wrote: >>>> On 28/04/2010 4:25 p.m., Nicholas Sherlock wrote: >>>>> Is this supposed to work? >>>> >>>> Nobody knows if Cygwin signals work? Could anybody reproduce the crash >>>> from my example code at least on their machines? >>> >>> Investigating this is on my todo list. >>> >>> cgf >> >> Okay, thanks :) > > I have confirmed that the bug exists on w2ksp4, so it's not a Win7, 64-bit >or UAC or DEP thing; looks like a real bug in the Cygwin DLL. Corinna and I have been discussing this in private email so I know this is a real problem. I just don't have a concentrated block of time to track it down yet. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple