X-Spam-Check-By: sourceware.org Date: Wed, 29 Mar 2006 18:25:06 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 20060301 snapshot and later. sh hangs with very long command line Message-ID: <20060329232506.GD12890@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <98A22DD7-2111-489A-9843-E0176048A2BB AT rehley DOT net> <20060313000602 DOT GA19770 AT trixie DOT casa DOT cgf DOT cx> <442B14EE DOT 5AEFA518 AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <442B14EE.5AEFA518@dessent.net> User-Agent: Mutt/1.5.11 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 Wed, Mar 29, 2006 at 03:14:54PM -0800, Brian Dessent wrote: >Christopher Faylor wrote: >>>I was building binutils using the cygwin 20060308 snapshot, and when it >>>did the check for "finding the maximum length of command line" a sh >>>shell goes to 99% cpu usage and doesn't return until I end the process >>>using task manager. >>> >>>I isolated the portion of the script that was hanging and was able to >>>repeat the problem. The script hangs when it checks for a command line >>>of length 16384. This happens every time I run the script, and it is >>>reproducible for me on at least windows 2000 and windows XP. I've >>>attached a test script. >>> >>>The problem doesn't happen with the 20060227 snapshot, but appeared in >>>20060301 and later versions. It is present in the 20060309 snapshot. >> >>Thanks for the test case. This should be fixed in the next snapshot. > >This looks like it has regressed. I am using CVS HEAD as of yesterday >and have run into the "finding the maximum length of command line >arguments" hang in configure scripts. Peter's testcase fails too. As >a workaround I've set cygexec on my mounts which seems to workaround >the issue (and allows larger commandlines anyway.) Would you be willing to track down the snapshot when this started failing again? 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/