This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: BUG: ualarm(0,0) not clearing ualarms
On Tue, Feb 14, 2006 at 11:08:52AM -0500, Robb, Sam wrote:
>Gary R. Van Sickle wrote:
>> I get the same can't-duplicate as Chris does, on 'uname -a'=
>>
>> CYGWIN_NT-5.1 DFW5RB41 1.5.20s(0.153/4/2) 20060209 14:37:47
>> i686 Cygwin
>>
>> I don't have any of this stuff in $CYGWIN, might be worth a
>> try to ditch it:
>>
>> "
>> CYGWIN = 'server ntsec forkchunk:32768'
>> "
>
>Chris, Gary, et al,
>
> 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.
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/