X-Spam-Check-By:	sourceware.org
From:	"William Sheehan" <william DOT sheehan AT openinterface DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: 1.5.20-1 perl 2328 sig_send: wait for sig_complete event failed
Date:	Thu, 13 Jul 2006 17:42:14 -0700
Message-ID:	<002b01c6a6de$59b25dd0$280aa8c0@oius.com>
MIME-Version:	1.0
X-Mailer:	Microsoft Outlook, Build 10.0.6626
In-Reply-To:	<44B6C58D.3070800@cygwin.com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id k6E0gSHb017714

Thank you for the snapshot advice; right now (well, into tomorrow and
possibly Monday) I will be doing a binary search of the installation
snapshots to try and track down the offending diff.  The latest snapshot
exhibits the same behavior.  So far I have narrowed the problem down to
between Feb 03 and May 25.

You were correct about the Perl version; downgrading it did not fix the
issue.  I did notice that downgrading the 'cygwin' package did fix the
issue, even when combined with the latest perl.  So it seems we're on the
right track.

I knew the UNC in the path would come up!  This machine is only automated
operations under normal circumstances.  Every binary required by the scripts
is either before the UNC path or executed with a modified PATH variable, and
since the scripts don't make typos, it hasn't been an issue.  As to why the
UNC path is still there, given that we don't use it...hmm, question of the
year :)

William Sheehan
Builds Engineer / Network Administrator
Open Interface North America

-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of
Larry Hall (Cygwin)
Sent: Thursday, July 13, 2006 3:14 PM
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.20-1 perl 2328 sig_send: wait for sig_complete event failed


William Sheehan wrote:

<snip>


> 
> -----------------------------------------------------------------
> Environment details
> -----------------------------------------------------------------
> 
> I have attached the cygcheck output per the problem reporting 
> guidelines.

This has nothing to do with your problem (at least not obviously) but don't
you find having a UNC path in your PATH to be real slow?

<snip>

> 
> -----------------------------------------------------------------
> Possible solution paths?
> -----------------------------------------------------------------
> 
> * I read in the guidelines that it is generally not advisable to 
> mention that these scripts worked with the previous versions of 
> Cygwin.  One idea I had was to try some older versions of Perl from 
> the Cygwin setup and see if the problem still occurs.  Should I go 
> through with that idea?


I'd say that if you're willing to try variations on a theme, you're better
off trying the latest and greatest snapshot of the Cygwin DLL from
<http://cygwin.com/snapshots/>.  The only other version of Perl that's
available is from a year ago January so if you last updated 5 months ago,
your Perl hasn't changed in this last round.


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

--
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/




--
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/

- Raw text -