Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Content-Type: text/plain; charset="iso-8859-1" From: Christopher Charles January To: cygwin AT cygwin DOT com Subject: Re: problem with handle_to_fn ? Date: Mon, 3 Jun 2002 13:30:46 +0100 References: <002f01c20a20$0064c330$0100a8c0 AT advent02> <20020602165449 DOT GA13484 AT redhat DOT com> <20020603033750 DOT GA8944 AT redhat DOT com> In-Reply-To: <20020603033750.GA8944@redhat.com> MIME-Version: 1.0 Message-Id: <200206031330.46435.chris@atomice.net> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g53CV6b05498 On Monday 03 Jun 2002 4:37 am, Christopher Faylor wrote: > On Sun, Jun 02, 2002 at 12:54:49PM -0400, Christopher Faylor wrote: > >On Sun, Jun 02, 2002 at 11:26:47AM +0100, Chris January wrote: > >>With the recent changes in grabbing the path of a file from its open file > >>handle I'm seeing the following: > >>Initially the path is as follows: > >>\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\...... > >>but later it gets translated to: > >>/cygdrive/c/Device/HarddiskDmVolumes/PhysicalDmVolumes/BlockVolume1/... > >>which then gets translated back to: > >>c:\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\.... > >>which AFAIK is an invalid path... > > > >Even if this function fails, the net result should be no different than > >what cygwin used to do. It always used an invalid path in that scenario. > > > >Are you actually seeing failures related to this? > > FWIW, I couldn't duplicate this but I did take a stab at fixing the > problem. handle_to_fn was doing the wrong thing with network drives. I > fixed that, too. To duplicate try something like strace cat file >someotherfile. I think that should work. Chris -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/