Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Tue, 5 Jul 2005 10:07:46 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Freeze in perl script after cygwin upgrade 1.5.17 -> 1.5.18
Message-ID: <20050705140746.GB26948@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <42C96709 DOT 9030005 AT scytek DOT de> <42C9C261 DOT 4080502 AT scytek DOT de> <20050704232944 DOT GD20441 AT trixie DOT casa DOT cgf DOT cx> <42C9C8BB DOT 1030308 AT scytek DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <42C9C8BB.1030308@scytek.de>
User-Agent: Mutt/1.5.8i

On Mon, Jul 04, 2005 at 07:39:39PM -0400, Volker Quetschke wrote:
>>>It is a standalone testcase, unfortunately it depends on the absolute path
>>>it resides in. To reproduce unpack perlfreeze.zip to d: and then
>>>do:
>>>$ cd /cygdrive/d/perlfreeze
>>>$ ./perltest.pl
>>>
>>>and see it hang. (In rxvt/bash)
>>
>>I've downloaded this and it does just sit there but I don't know how long 
>>I'm
>>supposed to wait.  Is it supposed to print a lot of stuff right away?
>Yes, it's supposed to produce a cab file while reporting what it is doing.
>
>I realized that if you press CTRL-c it really starts to build the cab file,
>but it doesn't produce any screen output.
>
>You can uncomment the
>  $extracmd='sleep 1 && ';
>line in the script and see what should happen.

Last night's snapshot should fix this problem.

http://cygwin.com/snapshots/

cgf

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