X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.4 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY
X-Spam-Check-By: sourceware.org
X-Yahoo-SMTP: jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o-
Date: Wed, 6 Jul 2011 12:54:10 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: "openssl speed" hangs on cygwin
Message-ID: <20110706165410.GA4679@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <31999889.post@talk.nabble.com> <20110706072134.GD23717@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110706072134.GD23717@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Wed, Jul 06, 2011 at 09:21:34AM +0200, Corinna Vinschen wrote:
>On Jul  5 12:56, smujushi wrote:
>> 
>> I have an issue when running "openssl speed" on either a 64 bit Windows 7 PC
>> (Intel Core i7 870 2.93GHz) or a 64 bit Windows 2008 R2 Std Server (Xeon
>> X5450 3GHz) under Cygwin. "openssl speed" runs fine on all the other *Nix's
>> I manage.
>> 
>> It hangs either after the first line or maybe the next 6 or 7 lines, it's
>> variable. I tried doing a time on the command and it didn't complete after
>> over an hour where I had to Control-C to stop the execution.
>
>Just FYI, I can reproduce this problem.  For some reason it seems to
>occur only on systems with more than one CPU.  I have no idea why
>this happens, but I'll try to find out.

Thanks to Corinna's debugging, I believe I was able to fix (or at
least work around) this glitch in signal handling.

It works for me with the latest snapshot:

http://cygwin.com/snapshots/

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

