X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Message-ID: <4C63FB24.3060204@kitware.com> Date: Thu, 12 Aug 2010 09:46:12 -0400 From: Bill Hoffman User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.11) Gecko/20100711 Lightning/1.0b1 Thunderbird/3.0.6 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: git and openssh issue (eblake?) References: <4C45D041.8010209@kitware.com> <4C4677CA.2090608@bopp.net> <4C485D3D.7070307@kitware.com> <4C4862F6.7090602@bopp.net> <4C48A06F.6020309@kitware.com> <4C48C9B3.60602@bopp.net> <4C48EE1A.1040705@kitware.com> <4C49BD97.6080103@bopp.net> <20100723162754.GA8455@ednor.casa.cgf.cx> <4C56D167.2010904@kitware.com> In-Reply-To: <4C56D167.2010904@kitware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 8/2/2010 10:08 AM, Bill Hoffman wrote: > On 7/23/2010 12:27 PM, Christopher Faylor wrote: > >>> Cygwin Package Information >>> Package Version Status >>> cygwin 1.7.5-1 OK >>> git 1.7.1-1 OK >>> openssh 5.5p1-2 OK >>> >>> I haven't tried the other configurations I mentioned yet, but if there >>> is someone who has the ability to debug this in more depth, this looks >>> like a quick and readily reproducible test case. >> >> I checked this out and it looks like something in git is overflowing >> and scriblling on the stack. I was hoping that it would be a cygwin >> problem which I could fix (and I wouldn't be surprised if it eventually >> turned out to be) but I didn't see much evidence of the DLL causing this >> problem. It looks like it is git itself doing something wrong. >> >> Eric do you have the cycles to check this out? It is pretty easy to >> reproduce. >> > > How did you come to the conclusion that it was a stack overwrite? I > would be willing to look at this a bit(not that I know much about git > internals). However, it would be helpful if I could see how you came to > that conclusion? > Is anyone looking at this? 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