"run" changes behavior with cygwin-17.6

Christopher Faylor cgf-use-the-mailinglist-please@cygwin.com
Wed Aug 18 18:54:00 GMT 2010

On Wed, Aug 18, 2010 at 07:32:40PM +0100, Andy Koppe wrote:
>On 18 August 2010 19:24, Christopher Faylor wrote:
>>>I noticed a similar change in cygstart, too. I used to have a script
>>>that would cd to a directory and then run cygstart. After the upgrade to
>>>1.7.6, this stopped working. I had to use the --directory switch to
>>>cygstart to get the right behavior.
>> Call me dense but I don't understand why any changes are needed. ??If
>> you're cd'ed to a non-Cygwin-special location why doesn't stuff "just
>> work"?
>The Win32 working directory is changed to '\\?\PIPE\' at process
>startup, otherwise the working directory can't be deleted from under
>the process, which you can do on Linux.

Yes, I guess I did not properly appreciate the fact that we presumably
broke every CreateProcess call in a cygwin program when we did this.
While I'm on record about not caring too much about that scenario, it
seems meaner than usual for us to break this since the report which
caused the recent change was from someone calling CreateProcess in a
cygwin program.

But, anyway, since we have broken this, I don't think we should force
every user of CreateProcess to call CYGWIN_CONV_TO_POSIX_PATH.  We
probably should add an internal interface which sets the current working
directory for windows if it can.


Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

More information about the Cygwin mailing list