X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 14 Jul 2008 22:02:15 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: 1.7 constantly accesses floppy drive Message-ID: <20080714200215.GA4313@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <7CDD82AEE5144D60961BDAD9B1C1A40D@cit.wayne.edu> <4877A0FE.1070002@cygwin.com> <4877B123.3080409@cygwin.com> <4877D782.4000308@cygwin.com> <15E6E2FA521344A3B74D38BA78E2D7DF@cit.wayne.edu> <487B89EA.7060503@cygwin.com> <20080714175024.GB24644@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080714175024.GB24644@calimero.vinschen.de> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Jul 14 19:50, Corinna Vinschen wrote: > On Jul 14 13:16, Larry Hall (Cygwin) wrote: > > Lee Maschmeyer wrote: > >> Attached is the output of the command: > >> strace -o strace_ls.log ls 1.7-log.txt > >> I don't think it tells us anything we didn't know. Cygwin, down under the > >> hood, thinks Windows is on a: but all its variables show that it's on c:, > >> as do Windows variables. > > > > To me this suggests that there could be a problem with getwinenv() but > > I can't say more than that at the moment. > [...] > I'll try to figure out the cause of this problem. Found it. I introduced a subtle bug in Cygwin's strncasecmp function. Will be fixed in the next 1.7.0 test release. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/