-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
git-bash.exe not working when git installed in root (e.g. D:\Git) #509
Comments
which version? |
2.6.2 64-bit |
This problem is also present when doing a "classic" install for Git-2.6.2-32-bit (problem exists also in Git-2.6.1-32-bit). During installation, git-bash.exe (63439d2b6980835d1f67e8ac7260dd050ffdbb87) is copied to "C:\Program Files (x86)\Git" and then at the end of the installation process, git-bash.exe is truncated to a 27kB file (596b198418a97437718d26ef920b9c5a4a964aee). The resulting truncated git-bash.exe is considered malware for some AV (https://www.virustotal.com/fr/file/9f9b2f190b5bd91a42a3e8ee09f0edc12254ba7c18ede54cb4382d512a55c1f8/analysis/1445947552/). The truncation is mainly the removal of end data starting at : <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">. |
@tavrez I cannot reproduce here. Installing with |
I've tested installation process near 8 times after this, as I got it's related to length of the folder, all this folders failed when I tested: |
Finally got it... |
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes git-for-windows#509 Signed-off-by: Johannes Schindelin <[email protected]>
This topic branch waited a long time to be completed, and the final push was provided by the need to investigate the reason for the bug reported in git-for-windows/git#509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes git-for-windows#509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes git-for-windows#509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes git-for-windows#509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
To be precise: when the value of the environment variable is shorter than its name, we have to move the remaining bytes *after* expanding the environment variable: we would look for the wrong name otherwise. When the value is longer than the name, we still need to move the bytes out of the way first, to avoid overwriting them with the interpolated text. This fixes #509 Signed-off-by: Johannes Schindelin <[email protected]>
…gcc-12-msftgit ci: fix `windows-build` with GCC v12.x
I tested this only with default terminal emulator being command prompt. Git-bash.exe will says "cannot find the file"
The text was updated successfully, but these errors were encountered: