Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Thu, 23 May 2002 01:38:04 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: path_conv::check() gets confused by recently opened files Message-ID: <20020523053804.GA31025@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20020521200309 DOT GA2392 AT tishler DOT net> <20020522145627 DOT G10218 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020522145627.G10218@cygbert.vinschen.de> User-Agent: Mutt/1.3.23.1i On Wed, May 22, 2002 at 02:56:27PM +0200, Corinna Vinschen wrote: >I found that path_conv::check() pinches off the tail when searching >for existing path components. This strips the filename here from >path_copy since it doesn't exist yet. The effect is that >path_conv->normalized_path can't be correct when path_conv points >to a yet non-existant file. I don't see an easy way to get the >correct normalized path without introducing an additioanl temporary >copy of the path. I've duplicated the problem. I'll fix it tomorrow. I had to get my gcc working again. I'm getting random core dumps from cygwin now but I think it's gcc related. cgf