Date: Thu, 15 Nov 2012 15:55:45 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: git fork failure on pull with a workaround (hopefully a clue for a fix)
Message-ID: <20121115205545.GA14187@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <509AB02F.1000300@kitware.com> <509AC4E0.2080709@bopp.net> <509BC18E.1050905@kitware.com> <50A545D3.1060209@kitware.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50A545D3.1060209@kitware.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

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 around the crash is here:

Question: What are the odds that a posted strace snippet would not
contain anything useful for debugging a problem?

Answer: Nearly 100%

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.

cgf

--
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