X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-3.8 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL
X-Spam-Check-By:	sourceware.org
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=7Yk11oDItOahd20xrbha3/sc3vyQ0Wi/5jM/9lGIlXo=; b=Yly1MB/mvAYufzRW6WLPHm9fBlFz0bUV9sOSgqghxuYzuqD6p6bHQ1TeHMPELnLsqx Yp1F9msX1G74u6OrYkIHaqoSH7/HdqEr0A3v0NSId+XkAi2JFyrOjO0AvCxxhv1XQtBx ZePQ71n3aWeBX0pTqWgte21kRYvBHCe7u8XTS3xAvpbOVklD3dQiDhGfxnN5Mgb/lb48 82JHmaJfiWOeyxW7hTzC+yJIrWo1ddcyH8nzCBqgt1chHTxzyZ8F/Qtyf4QY++5g7Y6r MqEiumS2jtWa6S3YAThyRip0CFPaa6y38FMwN5o6PM/MM12MfiC9VhcBaRUx0zWOTBq0 5+TQ==
Message-ID:	<50A55E87.3060304@kitware.com>
Date:	Thu, 15 Nov 2012 16:28:39 -0500
From:	Bill Hoffman <bill DOT hoffman AT kitware DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: git fork failure on pull with a workaround (hopefully a clue for a fix)
References:	<509AB02F DOT 1000300 AT kitware DOT com> <509AC4E0 DOT 2080709 AT bopp DOT net> <509BC18E DOT 1050905 AT kitware DOT com> <50A545D3 DOT 1060209 AT kitware DOT com> <20121115205545 DOT GA14187 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To:	<20121115205545.GA14187@ednor.casa.cgf.cx>
X-Gm-Message-State:	ALoCoQnFL5BOj7Pd8uof2hvTaSnlLa0+M2y+DHT/vlPfxdt8pXckrxc3jqWpgDKE+uTDegy8BaGoXMpImW8L1QoFNM+NaYToAuc7RQ7URGIiVFmZ8qSWINtJnGPpHc1YUmUdHWW192a9J7sdy4o/+NuUYwW6c0Y48g==
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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 tell me how to attach a debugger to 
that process given that information.  It was admittedly a bit of a 
stretch.

> The answer to your question, which will probably be taken as flip, is:
> you can debug the problem by diving into the cygwin source code.  If it
> isn't just a simple rebase problem then the solution would lie there.

Since it works with a smaller length PATH I would also think that rebase 
would help. I have recently run rebase with no errors for what that is 
worth.

 From your comment, I would take it that you think that the issue is in 
the cygwin dll itself and not bash or git.

So, I guess you would suggest building a debug cygwin dll, and then 
using gdb on git to try and find out where fork fails?

Thanks.

-Bill


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -