-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Git Bash Errors in 2.7.0.2 #649
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
Comments
Thanks for this very thorough bug report. Could you install 2.7.0(2) again, then run a cd C:\Program Files\Git\usr\bin
dash -c 'rebaseall -p' This is of course only a shot in the dark, but your report reminded me of the 32-bit issues we had. Maybe they now affect 64-bit as well. |
Thanks for the help. The response to the dash command is:
This is strange though because rebaseall is in that directory. Edit: After reading the linked article, I tried the following command:
This was run from an administrator command prompt. |
Actually, you were so close: |
I have the same issue - unfortunately, I still get the |
FWIW, I was able to solve this by repeatedly running |
If you installed to |
@dscho, I got the "Permission denied" error running the command as administrator (yes, I triple-checked ;-) ). |
@mhils ah, well, you were a bit sparse with your info. You mentioned only that there are Permission denied errors. There are permission denied errors that are 1) legitimate and 2) harmless: Take-home lesson: be generous in the information you provide and the output you copy & paste. |
I was also getting the permission denied error while running the rebaseall command as an administrator. I have noticed that 2.7.0(0) works, while 2.7.0(1) and later does not. I'm wondering if the ASLR support has something to do with this problem. I did a little research and https://en.wikipedia.org/wiki/Address_space_layout_randomization#Microsoft_Windows states that HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\MoveImages must be enabled for ASLR to work. Both my and my co-workers' machines are IT controlled and neither has this registry entry. Another thought is that our IT-supplied anti-virus (Cylance) is preventing the rebase from working. |
Aaaargh! Again no context? Just mentioning that there was some permission denied error? I'll bow out of this ticket. |
All of the context is in my previous comment from four days ago, but I will copy it here for you: After reading the linked article, I tried the following command:
This was run from an administrator command prompt. The linked aticle is the 32-bit issues articly you mentioned. I can't offer any additinoal context because the rebase command isn't returning any. |
If you read your initial report, you will see plenty of "Permission denied" errors there. So simply referring to "permission denied errors" later (and not mentioning at all that the dash invocation produced them) was prone to be confusing. You will have to admit so much. As it is, I think |
Thank you for the help. With Git for Windows version 2.7.1, I ran the following command from an administrator command prompt:
I'm sorry I cannot provide any additional context. This is all that is returned by the command. I appreciate the help you have provided so far. |
Okay, next try. Can you run an interactive dash: C:\Program Files\Git\usr\bin> dash It should print a ./cat rebaseall and see the content. If that works, ./dash -x rebaseall -p should print a list of commands as they are executed, together with some output, if any. |
I'm getting similar (but not identical errors) to @strohm-a. I just upgraded from 2.7.0 to 2.7.1.2 (32-bit) and the first time I ran git bash, I got these errors...
Subsequent runs of git bash now always show this...
The 32-bit version of 2.7.0 was working fine. |
@cs96and ... and probably you are not running this Git Bash as administrator, correct? Already @strohm-a's initial report pointed out the need to run Git Bash as admin to correct the Anyway, let's not distract from @strohm-a's problem with an almost unrelated issue. @strohm-a did you have a chance to run |
Sorry I missed the part that mentioned running as administrator fixed it. I have done this now and the errors have gone. Shall I create a separate bug report for this? |
@cs96and if the problem persists, yes. Anyway, let's not distract from @strohm-a's problem with an almost unrelated issue. @strohm-a did you have a chance to run |
I tried running the dash shell from an administrator command prompt. The two dash commands I tried resulted in a "died waiting for dll loading" error.
|
@strohm-a are you positively certain that no MSYS2 process is running in the background? Could be the ssh-agent, for example, or any other Git Bash (or even a sh.exe that was not properly terminated)? |
Just to make sure, I installed 2.7.1.2 and rebooted my machine. I then logged in and tried running the dash terminal commands from an administrator command prompt and received the same "died waiting for dll loading" errors as before. Here is the output from the Windows tasklist command:
|
@dscho |
@White-Tiger no, there was not enough information to figure this out. If that really was the issue, then |
No.. that command returns: but I guess it won't help much with this issue... yet someone has to fix the rebaseall script so it can be run directly ;) |
This being Open Source, it is reasonable to expect this someone to be yourself. ;-) |
I am having the same issue with the latest version of Git-2.7.2-64-bit. When I run the commands dash -x rebaseall -p, I get it executed with Exit Code 0. However, I still get the error when I run the Git-Bash ("C:\Program Files\Git\git-bash.exe" --cd-to-home). I don't get errors when I run Git-CMD ("C:\Program Files\Git\git-cmd.exe" --cd-to-home) |
@psrin7 do you get the same error messages? If so, maybe you can shed some light into the problem by starting up Process Monitor and figuring out which |
I'm getting this issue as well, even with Edit: Also FWIW, if I install msys2-x86_64-20160205 and run the commands from one of it's shell windows, all the normally breaking git commands run fine. So if that helps you narrow down the differences in msys2. |
@OverlordQ |
It seems that I analyzed a similar problem in a different ticket. If there is anybody out there who experiences the issue reported in this ticket and who could follow the indicated steps to rebuild and test the MSYS2 runtime with the indicated debug messages enabled, that would be totally awesome! |
I would but trying to get the SDK installed throws the same error.
|
Could you give https://github.com/git-for-windows/git/releases/tag/prerelease-v2.10.0.windows.1.11.geda474c a try? @OverlordQ that looks as if the same problem occurs inthe SDK itself, bummer. If the prerelease fixes the problem, I will release a new SDK version with the fix (but I won't have time before October to do that). |
No go.
PowerBroker
Basically if it uses git.exe directly it works, if it has to use the bash shell (sh.exe) it'll give the above error. |
What's that? |
Sorry, thought I updated my response again. It does look like PowerBroker is the culprit, it's some horrible enterprise software that injects itself everywhere. Rename one of it's dll's, which I think, prevents injection, and everything runs fine, so I'm pretty sure this isn't a git4win issue. |
Thank you for confirming! |
I installed Git 2.7.0 for Windows over 2.6.0 on 64-bit Windows 8 and I get the following output when I run bash.exe or sh.exe:
Running git-bash.exe gives the following output:
I can correct the second issue by running git-bash.exe as administrator once.
If I replace 2.7.0 with 2.6.0, the problems go away.
A co-worker is having the same problem on a new 64-bit Windows 7 computer as well.
The text was updated successfully, but these errors were encountered: