X-Spam-Check-By: sourceware.org Date: Fri, 27 Jan 2006 01:08:47 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: SIGALRM is ignored in generated code blocks (using mmap) - testcase included Message-ID: <20060127060847.GA14661@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <5.0.0.25.2.20060125101316.00bc8a30@pop3.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.0.0.25.2.20060125101316.00bc8a30@pop3.demon.co.uk> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Wed, Jan 25, 2006 at 10:19:14AM +0000, Lee Moore wrote: >>>Mmm, IIRC signals can't be delivered unless you call cygwin functions. >> >>If that is actually true, it's a bug. Cygwin should be able to >>interrupt user code. It doesn't try to interrupt... >> >>>int main(void) { >>> signal(SIGALRM,handler); >>> alarm(1); >>> Sleep(); >>>} >> >>...a Windows function like Sleep. It should interrupt, e.g., a busy >>loop in user code, however. > >are we agreed that this is a bug ? >If so how can I get a fix, or a workaround to get me further ? This may be fixed in the latest snapshot, which I'm generating right now. 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/