-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Git Bash: Segmentation Fault for every command #1832
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
What anti-virus scanners are being run on your machine. They have given problems in the past. If you don't integrate with VSCode, does it still seg fault? |
@PhilipOakley I have Windows Defender and Trend Micro Security Agent. No, if I run Git Bash in a standalone terminal from the start menu it works fine. (I believe it starts from It's only when I run it from within VSCode that this is an issue. |
Sounds like #1291 (comment) |
@jryd, you did mention that Git Bash works fine in the original report. But does |
@michaelblyons i had searched yesterday but hadn't come across that issue, it is the same error and same circumstances. It looks to be an antivirus issue, I turn it off and it all works fine again. I will talk to my IT department about getting an exclusion policy on the Git folder. |
Setup
defaults?
to the issue you're seeing?
The issue seems to only occur when I start Git Bash directly from
C:/Program Files/Git/bin/bash.exe
, which I use to be able to have Git Bash integrated with VSCode. If I run Git Bash throughC:/Program Files/Git/git-bash.exe
then it runs fine.Details
I am running Git Bash within VSCode, as mentioned above.
Minimal, Complete, and Verifiable example
this will help us understand the issue.
Literally every command I run returns a segmentation fault, except
pwd
.For the appropriate command to run
Segmentation fault is returned and a file named
bash.exe.stackdump
appears. Below are the contents:I have tried reinstalling Git, different versions of Git, running as administrator, updating Windows etc, all to no avail.
This is happening in all directories, regardless of whether it is a repository or not.
The text was updated successfully, but these errors were encountered: