x86_64 Cygwin 1.7.29: possible bug to trace symlink (Win7)

[Corinna Vinschen]

On Apr 16 03:39, 卜勇华 wrote:
> Hi Corinna,


Please don't top-post.  Thank you.


> Below is what I get:
> RS-I9E3U8R4:[~/tmp/test_symlink]>uname -a
> CYGWIN_NT-6.1 RS-I9E3U8R4 1.7.29(0.272/5/3) 2014-04-07 13:46 x86_64 Cygwin
> RS-I9E3U8R4:[~/tmp/test_symlink]>echo $CYGWIN
> winsymlinks:nativestrict
> RS-I9E3U8R4:[~/tmp/test_symlink]>echo test > test.txt
> RS-I9E3U8R4:[~/tmp/test_symlink]>mkdir dest
> RS-I9E3U8R4:[~/tmp/test_symlink]>cd dest
> RS-I9E3U8R4:[~/tmp/test_symlink/dest]>ln -s ../test.txt test.txt
> RS-I9E3U8R4:[~/tmp/test_symlink/dest]>cd ../
> RS-I9E3U8R4:[~/tmp/test_symlink]>mkdir src
> RS-I9E3U8R4:[~/tmp/test_symlink]>cd src
> RS-I9E3U8R4:[~/tmp/test_symlink/src]>ln -s ../dest dest
> RS-I9E3U8R4:[~/tmp/test_symlink/src]>cd ../
> RS-I9E3U8R4:[~/tmp/test_symlink]>cat src/dest/test.txt
> cat: src/dest/test.txt: No such file or directory

I can reproduce it now.  I made a mistake when creating the symlinks
the first time, which is, I created them with tcsh.  Tcsh tends to
change relative paths using ".." components to absolute paths on the
command line.  Using plain relative paths, I now see what's going on.

But it'sa tricky problem.  I don't know how to fix it yet.  I'll
have to think about it, so please be patient.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20140416/5202e4d9/attachment.sig>