X-Spam-Check-By: sourceware.org Date: Thu, 13 Jul 2006 11:06:01 -0700 From: Yitzchak Scott-Thoennes To: cygwin AT cygwin DOT com Subject: Re: Perl failure Message-ID: <20060713180601.GA3872@efn.org> References: <20060713155309 DOT GA1648 AT efn DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060713155309.GA1648@efn.org> User-Agent: Mutt/1.4.2.1i 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 On Thu, Jul 13, 2006 at 08:53:09AM -0700, Yitzchak Scott-Thoennes wrote: > On Wed, Jul 12, 2006 at 05:08:43PM -0700, Bruce Dobrin wrote: > > Hi, > > > > I have a server that has been doing back end maintenance using perl on > > cygwin for 6 years now. I recently upgraded from win2k and cyg1.5.9 to > > XP sp3 and cyg1.5.19 (to be fare, I also cleaned up the perl code a > > bit). The script checks versioning and build info on about 600+ windows > > systems. Since the upgrade, it gets thru about 500 of them ( almost > > exactly 2 hours) and then: > > > > panic: MUTEX_LOCK (45) [util.c:2266] at > > /c/dist_and_install_files/source/dist2/spUpdate2d.pl line 24, > > line 277. > > panic: MUTEX_LOCK (45) [op.c:354], line 277. > > This indicates EDEADLK being returned from posix_mutex_lock. Err, I mean pthread_mutex_lock. -- 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/