X-Spam-Check-By: sourceware.org Date: Mon, 13 Feb 2006 15:03:34 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: BUG: ualarm(0,0) not clearing ualarms Message-ID: <20060213200333.GA14798@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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060213125813.fb30e530d17747c2b054d625b8945d88.ad58bcc497.wbe@email.secureserver.net> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 12:58:14PM -0700, Jerry D. Hedden wrote: > 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. I'm not really interested in the Perl version of the bug. I thought that the test case which you forwarded demonstrated the problem. >The C code I sent, produced the bug on my work computer. I'll try my >home computer this evening. Is it possible that something in my >environment is the problem? I don't know what it would be, if so. Btw, please don't use raw email addresses in the body of your messages and please *attach* the cygcheck output. Don't just include it inline in your message. 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/