This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: problem with handle_to_fn ?

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.


Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]