I'm getting this now, I get it not just on git pull but also on git branch,
git status, and others. I've got a script that gives me status on a series
of repos and the for failure happens perhaps 1 in 10 repos that are
inspected. If I do a series of git pulls, it happens constantly.
The bug
On 3/16/2013 11:31 AM, CraigMurray wrote:
I'm getting this now, I get it not just on git pull but also on git branch,
git status, and others. I've got a script that gives me status on a series
of repos and the for failure happens perhaps 1 in 10 repos that are
inspected. If I do a series of
On Nov 8 09:28, Bill Hoffman wrote:
On 11/7/2012 3:30 PM, Jeremy Bopp wrote:
On 11/07/2012 01:02 PM, Bill Hoffman wrote:
Is there a
way to debug this?
The first step is to follow the problem reporting guidelines:
http://cygwin.com/problems.html
Following them may reveal a
Greetings, Corinna Vinschen!
Is there a
way to debug this?
The first step is to follow the problem reporting guidelines:
http://cygwin.com/problems.html
Following them may reveal a conflicting cygwin.dll file or something
similar in your full path which is interfering with some git
On Nov 23 16:32, Andrey Repin wrote:
I *think* this is an issue between Windows and Cygwin for which there's
no easy solution. The memory layout created by Windows can move the
main stack address in a child process depending on the size of the
environment.
I observed this myself, but
On Fri, Nov 23, 2012 at 02:11:23PM +0100, Corinna Vinschen wrote:
On Nov 23 16:32, Andrey Repin wrote:
I *think* this is an issue between Windows and Cygwin for which there's
no easy solution. The memory layout created by Windows can move the
main stack address in a child process depending
Greetings, Christopher Faylor!
I *think* this is an issue between Windows and Cygwin for which there's
no easy solution. The memory layout created by Windows can move the
main stack address in a child process depending on the size of the
environment.
I observed this myself, but
On 11/8/2012 9:28 AM, Bill Hoffman wrote:
On 11/7/2012 3:30 PM, Jeremy Bopp wrote:
On 11/07/2012 01:02 PM, Bill Hoffman wrote:
Is there a
way to debug this?
Can anyone think of a way to debug this?
I ran strace, and the area around the crash is here:
181 1366752 [main] git 5908
On Thu, Nov 15, 2012 at 02:43:15PM -0500, Bill Hoffman wrote:
On 11/8/2012 9:28 AM, Bill Hoffman wrote:
On 11/7/2012 3:30 PM, Jeremy Bopp wrote:
On 11/07/2012 01:02 PM, Bill Hoffman wrote:
Is there a
way to debug this?
Can anyone think of a way to debug this?
I ran strace, and the area
On 11/15/2012 3:55 PM, Christopher Faylor wrote:
Question: What are the odds that a posted strace snippet would not
contain anything useful for debugging a problem?
Answer: Nearly 100%
Thought it might give a clue as to which process was not able to fork.
And that someone might be able to
Hopefully more useful information... :)
I used GIT_TRACE=1 to figure out where in the git pull things go bad and
found something potentially interesting.
I get the fork failure if I do this:
$ /cygdrive/c/cygwin/lib/git-core/git.exe 'fetch' '--update-head-ok'
2 [main] git 6380 fork:
I have seen others post about this, but have not seen a solution.
For git pull operations, and some other git commands, I get fork
failures like this: (happens with any repository, this is just an example)
$ git pull 2 [main] git 7384 fork: child -1 - forked process 7420 died
unexpectedly,
On 11/07/2012 01:02 PM, Bill Hoffman wrote:
Is there a
way to debug this?
The first step is to follow the problem reporting guidelines:
http://cygwin.com/problems.html
Following them may reveal a conflicting cygwin.dll file or something
similar in your full path which is interfering with
13 matches
Mail list logo
