Re: "run" changes behavior with cygwin-17.6

[Charles Wilson <cygwin at cwilson dot fastmail dot fm>]

On 8/18/2010 2:25 PM, Andy Koppe wrote:
> Ouch. This might affect even more cygutils. We really should have
> thought of that.
>
> At least there aren't any chdir() calls in any of the cygutils, so it
> should primarily be a question of setting the Win32 current directory
> in line with the POSIX one at startup, in any of the utils that may
> invoke a Win32 function with a relative path. Chuck, do you need a
> hand with going through them?

Oh, riiiiight.

The problem is this: since the win32 CWD is *always* bogus, it is 
possible that other win32 functions will croak, not just CreateProcess. 
 So, there are a number of native win32 calls in the cygutils tools, like:

cygstart: CreateProcess, among others
lpr: ...many...
putclip/getclip: GetClipboardData, SetClipboardData, etc

Now, I haven't tested each of these tools exhaustively under 
cygwin-1.7.6, so I'm not sure the bogus win32 cwd affects them (except 
obviously cygstart).  But...by their very nature many of these tools use 
the native w32api.  So...each should probably take care to set the win32 
cwd if at all possible.


Yeah, patches would be great.

--
Chuck

--
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