Date: Tue, 14 Feb 2006 13:10:39 -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: <20060214181039.GB21264@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <3D848382FB72E249812901444C6BDB1D03E051F8 AT exchange DOT timesys DOT com> <20060214162201 DOT GD17073 AT trixie DOT casa DOT cgf DOT cx> <43F21BD5 DOT 5090605 AT ateb DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43F21BD5.5090605@ateb.com>
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 Tue, Feb 14, 2006 at 01:05:09PM -0500, Reid Thompson wrote:
>>> I'm able to reproduce this on my machine, but only when I'm
>>>running it under rxvt.  If I run it from cmd.exe or within a
>>>standard cygwin bash shell, then it completes without the
>>>'-- BOGUS ALARM --' warnings.
>>>
>>> $ uname -a
>>> CYGWIN_NT-5.0 claus 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin
>>>
>>> $ gcc -o ua-test ua-test.c 
>>>
>>> $ ./ua-test.exe 
>>> First ualarm  - one shot
>>> Second ualarm - one shot
>>> Last ualarm   - repeats 3 times
>>> Clearing ualarm
>>> Sleeping
>>> --- BOGUS ALARM ---
>>> --- BOGUS ALARM ---
>>> Done
>>>    
>>
>>It behaves the same for me no matter where I run it.  I even increased the
>>final sleep time in case the program was exiting before the bogus alarm
>>was tripped.
>  
>my previous test case was run under rxvt as well, with no BOGUS ALARM's 
>noted.

Ditto, on both W2K and XP.

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/