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

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/