[ANNOUNCEMENT] Updated: vim-7.3.003-1

Christopher Faylor cgf-use-the-mailinglist-please@cygwin.com
Fri Aug 20 15:39:00 GMT 2010

On Fri, Aug 20, 2010 at 05:09:20PM +0200, Thorsten Kampe wrote:
>* Corinna Vinschen (Fri, 20 Aug 2010 16:33:17 +0200)
>> Not weird at all.  I could track this down to a point in Cygwin where
>> it neglects to close a handle to a symlink when instructed to follow
>> symlinks to their target.  I checked in a patch.  Please test the DLL
>> I uploaded at
>>   http://cygwin.de/cygwin-ug-177/newer-cygwin1.dll.bz2
>>   (md5sum compressed   5eab6680538279206bf23c54244825d2)
>>   (md5sum uncompressed e4833a601edad1571a9c6e0352a8e381)
>> which contains the fix.  This should not leave the stray handles to
>> vi, vim, etc in zsh.  And the side-effect should be that setup.exe
>> does not complain anymore in the original scenario.
>Yes, the evil handles are gone.

Sounds like a reason for a new cygwin release.

Did we ever come to a consensus on what to do with the Cygwin cwd stuff?
It sounded like people were reluctantly agreeing with my reluctant
proposal to not set the windows cwd to the pipe pseudo-location unless
chdir was explicitly called.

I'll throw another idea I had out there even though I don't think it's
something we want to do: We could scan the import table of the program
and see if any Windows API calls were used.  If they are don't do
anything special with the cwd.  This would be slow and not foolproof but
I thought I'd mention it anyway just to get the idea in the archive.


More information about the Cygwin-developers mailing list