Message-ID: <4B847902.4060209@shaddybaddah.name>
Date: Wed, 24 Feb 2010 00:55:30 +0000
From: Shaddy Baddah <helium@shaddybaddah.name>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: perl panics with cygwin snapshot
References: <4B837185.2030200@shaddybaddah.name> <20100224004602.GB24591@ednor.casa.cgf.cx>
In-Reply-To: <20100224004602.GB24591@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Hi,

On 24/02/2010 12:46 AM, Christopher Faylor wrote:
> On Tue, Feb 23, 2010 at 06:11:17AM +0000, Shaddy Baddah wrote:
>> This might be related to
>> http://www.cygwin.com/ml/cygwin/2008-11/msg00021.html, I'm also seeing
>> perl fail with a panic *with the latest snapshot*. Eg.:
>
> It's very unlikely that a 1+ year old email thread would have anything
> to do with a recent change to a cygwin snapshot.

Yeah, it was a long shot, but included it just in case.

>> $ uname -a
>> CYGWIN_NT-6.1 ***-w7 1.7.2s(0.222/5/3) 20100222 16:51:26 i686 Cygwin
>>
>> $ /bin/autom4te-2.65 --help
>> panic: MUTEX_UNLOCK (1) [util.c:2641] at /bin/autom4te-2.65 line 93.
>>
>> Unlike that previous email, I have not tried to downgrade.
>>
>> I also cannot kill the associated perl process:
>
> This should be fixed in the latest snapshot, or at least, I can't
> reproduce it with the simple case above.

Yes, this seems to have fixed it.

Thanks,
Shaddy

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