Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<3B6FCBC5.720C9785@paradise.net.nz>
Date:	Tue, 07 Aug 2001 23:06:45 +1200
From:	Edmund Horner <ejrh AT paradise DOT net DOT nz>
X-Mailer:	Mozilla 4.76 [en] (Win98; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Signal handling in tight loops

Hello again.

From my DJGPP days I remember that the alarm signal could not be raised
in very tight loops, because signals were only checked when memory was
accessed.  Does this apply to cygwin, by any chance?

The reason I'm asking is that I have a module in my program which I
can't completely trust, and I'd like to terminate it after 2 minutes if
it hasn't returned by then.  I'm hoping to use alarm() for this.

Feasible?



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -