Mail Archives: cygwin/2002/06/03/12:12:14
On Mon, Jun 03, 2002 at 01:30:46PM +0100, Christopher Charles January wrote:
>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.
That is the specific thing that the handle_to_fn is supposed to
accommodate. That is how I checked it.
So, still two questions "Are you seeing failures?" and "Are you still seeing
this behavior with the latest sources?"
cgf
--
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/
- Raw text -