This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: "run" changes behavior with cygwin-17.6

On 8/18/2010 1:12 PM, Charles Wilson wrote:
On 8/18/2010 11:09 AM, Corinna Vinschen wrote:
Looks like the "run" tool now needs a call to

CYGWIN_CONV_TO_POSIX_PATH ((get_cwd (), win32_cwd));

and then use win32_cwd in the call to CreateProcess.


Yep. run2 also needs a similar update.

Thanks for the heads up; I didn't really think about how the recent
changes to cygwin's cwd handling would affect those two packages.

The following patch seems to fix it for me. There will still be problems if the win32-converted cwd is (a) longer than 259 chars, or (b) derived from a cygwin-specific "virtual" path.

I don't want to duplicate all of cygwin's spawn_guts functionality in run, run2, and cygstart, so I think (a) and (b) are acceptable. After all, USUALLY you will invoke these tools via double-clicking some cygwin-specific or too-long paths are not an issue.


Attachment: run-cwd-fix.patch
Description: Text document

Attachment: run.exe.bz2
Description: Binary data

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]