Mail Archives: cygwin/2006/04/04/14:56:34
On Apr 3, 2006, at 4:25 PM, Christopher Faylor wrote:
> 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.)
>
> Out of curiousity, does this go away if you mount your /bin
> directory with
> the -X option? If so, the latest snapshot should fix it.
In the test case I used this seems to fix the problem, but when it is
running the real script, it still hangs. I'll try the snapshot to
see if the behavior is the same.
Peter
--
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/
- Raw text -