X-Spam-Check-By: sourceware.org From: "William Sheehan" To: Subject: RE: 1.5.20-1 perl 2328 sig_send: wait for sig_complete event failed Date: Fri, 14 Jul 2006 13:37:25 -0700 Message-ID: <005401c6a785$510af780$280aa8c0@oius.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <002b01c6a6de$59b25dd0$280aa8c0@oius.com> X-IsSubscribed: yes 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k6EKbdvX031986 I found the diff that seems to have caused the "wait for sig_complete event failed" problems I have been seeing. The offending diff occurred between 03/26 and 03/29, and there are entries in that ChangeLog that seem highly relevant as well. I did try the absolute latest snapshot at 1pm PST, which the snapshot page says was updated on 07/14. Unforunately, I am still seeing the same problems (though with different signal number and "unknown HEX" patterns, however those may be a red herring): 15 [unknown (0x828)] perl 3080 sig_send: wait for sig_complete event failed, signal -41, rc 258, Win32 error 0 15620 [unknown (0xF9C)] perl 3080 sig_send: wait for sig_complete event failed, signal -41, rc 258, Win32 error 0 60009717 [unknown (0x828)] perl 3080 sig_send: wait for sig_complete event failed, signal -34, rc 258, Win32 error 0 60025327 [unknown (0xF9C)] perl 3080 sig_send: wait for sig_complete event failed, signal -34, rc 258, Win32 error 0 120019442 [unknown (0x828)] perl 3080 sig_send: wait for sig_complete event failed, signal -34, rc 258, Win32 error 0 120035057 [unknown (0xF9C)] perl 3080 sig_send: wait for sig_complete event failed, signal -34, rc 258, Win32 error 0 180044824 [unknown (0x828)] perl 3080 sig_send: wait for sig_complete event failed, signal -34, rc 258, Win32 error 0 180044915 [unknown (0xF9C)] perl 3080 sig_send: wait for sig_complete event failed, signal -34, rc 258, Win32 error 0 240054553 [unknown (0x828)] perl 3080 sig_send: wait for sig_complete event failed, signal -40, rc 258, Win32 error 0 240085801 [unknown (0xF9C)] perl 3080 sig_send: wait for sig_complete event failed, signal -40, rc 258, Win32 error 0 305079392 [unknown (0x828)] perl 3080 sig_send: wait for sig_complete event failed, signal -40, rc 258, Win32 error 0 305110646 [unknown (0xF9C)] perl 3080 sig_send: wait for sig_complete event failed, signal -40, rc 258, Win32 error 0 Sorry for the double spacing; I just wanted to make sure the linebreaks appeared properly for everyone. As I mentioned above, the 03/26 snapshot (plus 03/04 and 02/03) work fine, and 03/29 through the absolute latest ones do not. I need to take off early today, but I will available again on Monday. I can reproduce this problem 100% and am more than willing to try any updated snapshots or generate any additional information, if given instructions. 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 William Sheehan Sent: Thursday, July 13, 2006 5:42 PM To: cygwin AT cygwin DOT com Subject: RE: 1.5.20-1 perl 2328 sig_send: wait for sig_complete event failed 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: > > ----------------------------------------------------------------- > 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? > > ----------------------------------------------------------------- > 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 . 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/ -- 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/