Date: Mon, 13 Feb 2006 14:50:50 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: BUG:  ualarm(0,0) not clearing ualarms
Message-ID: <20060213195050.GI7865@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20060213121845 DOT fb30e530d17747c2b054d625b8945d88 DOT 487b492f1c DOT wbe AT email DOT secureserver DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060213121845.fb30e530d17747c2b054d625b8945d88.487b492f1c.wbe@email.secureserver.net>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Mon, Feb 13, 2006 at 12:18:45PM -0700, Jerry D. Hedden wrote:
>I have encounted a bug in Cygwin whereby ualarm(0,0) is not clearing
>previously set ualarms.  This first cropped up while using Perl, but I
>was able to reproduce the bug with the following 'C' program.  The gist
>is that ualarm() is used several times, and then a final ualarm(0,0) is
>executed to clear them.  This is followed by a usleep().  The alarm
>signal handler shows that 'bogus' alarms are going off during the
>usleep().  Without the signal handler, the program would terminate
>prematurely due to uncaught SIGALRM.

Thanks for the test case but I don't see any difference in operation
between cygwin and linux when I run it:

    % ./ualarm.unix
    First ualarm  - one shot
    Second ualarm - one shot
    Last ualarm   - repeats 3 times
    Clearing ualarm
    Sleeping
    Done

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/