Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 14 Jun 2005 19:54:45 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: ls returns bad file descriptor Message-ID: <20050614235445.GD32250@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <018f01c57127$8f1553d0$3e0010ac@wirelessworld.airvananet.com> <20050614235245.GC32250@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050614235245.GC32250@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.8i On Tue, Jun 14, 2005 at 07:52:45PM -0400, Christopher Faylor wrote: >On Tue, Jun 14, 2005 at 07:49:42PM -0400, Igor Pechtchanski wrote: >>On Tue, 14 Jun 2005, Pierre A. Humblet wrote: >> >>> >> Please don't. Try doing this instead: >>> >> >>> >> c:\>strace -ostrace.out bash >>> >> shaffek>cd //explr_drivers5/reboot_results2 >>> >> reboot_results2 >>> >> shaffek>ls >>> >>> > Attached. >>> >>> Try turning off strict case checking. >> >>Pierre, would you mind elaborating on exactly what in that strace pointed >>you to strict case checking being the culprit? I've looked through it, >>but perhaps I missed something... Thanks. > >I don't know if Pierre picked up on something else (or maybe just looked >at the cygcheck output) but a clue was the fact that path_conv::check >kept inspecting components of the path even after a valid path was >detected. I was working my way there when I wisely decided to check the >mailing list and saw Pierre's insight. It's supposed to stop looking at >the path once it finds a valid path, except in the case of non-relaxed >case checking, i.e., this is one of a few slowdowns in the case checking >code. Btw, this should be fixed in the next snapshot. 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/