-
Notifications
You must be signed in to change notification settings - Fork 893
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rustup has trouble with cygwin #1508
Comments
This seems to be fixed for 64-bit Windows but not for 32-bit Windows. What's more, this problem occurs even when |
I think this bug is mistitled/analysed - the mismatched path separators don't prevent the msvc runtime (which the windows build of rustup is built with) don't prevent manipulating those files. I think its much more likely that something was holding a file lock open on the rustup-init.exe at the time removal is being attempted. To analyse this a system tracing tool like process monitor can be used to observe system activity while an update is running and the problem reproduced. (To verify the path separators can be mixed I wrote a quick test program:
which correctly created the file test in the relevant path. |
@mcandre are you able to get a procmon.exe trace of the file activity during an update that fails like this? we should be able to see a stale file handle from something (e.g. mcafee/defender/symantec) holding the file open and racing with the delete. If we can confirm that it is a third party we can add a retry wrapper similar to #1873 for the delete code path too. |
This is almost certainly #2441 |
When rustup is executed from a cygwin-like environment such as Git Bash, then it has trouble with file paths:
The text was updated successfully, but these errors were encountered: