X-Spam-Check-By: sourceware.org
Date: Mon, 13 Feb 2006 20:40:15 -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: <20060214014015.GC22733@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20060213125813 DOT fb30e530d17747c2b054d625b8945d88 DOT ad58bcc497 DOT wbe AT email DOT secureserver DOT net> <003801c63106$a78c1c60$020aa8c0 AT DFW5RB41>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <003801c63106$a78c1c60$020aa8c0@DFW5RB41>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Mon, Feb 13, 2006 at 07:33:26PM -0600, Gary R. Van Sickle wrote:
>> On Behalf Of Jerry D. Hedden
>> Sent: Monday, February 13, 2006 1:58 PM
>> Subject: RE: BUG: ualarm(0,0) not clearing ualarms
>> 
>> > -------- Original Message --------
>> > From: Christopher Faylor
>> >
>> > Thanks for the test case but I don't see any difference in operation 
>> > between cygwin and linux when I run it:
>> 
>> I know that Perl version of the bug occurred on both my work computer
>> (Win2K) and home computer (WinXP) both using the lastest Cygwin DLL.  
>> The C code I sent, produced the bug on my work computer.  
>> I'll try my home computer this evening.
>
>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'
>"

Btw, I have a hyperthreaded machine running at 3.06G with 1G of RAM.  I
wouldn't expect that to make a difference in this case, though.  I can't see
how this could be a N-processor race-related bug.

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/