From: Bill Hoffman <bill.hoffman@kitware.com>
To: cygwin@cygwin.com
Subject: Re: git and openssh issue (eblake?)
Date: Mon, 02 Aug 2010 14:08:00 -0000 [thread overview]
Message-ID: <4C56D167.2010904@kitware.com> (raw)
In-Reply-To: <20100723162754.GA8455@ednor.casa.cgf.cx>
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?
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
next prev parent reply other threads:[~2010-08-02 14:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 17:15 git and openssh issue Bill Hoffman
2010-07-21 5:48 ` Jeremy Bopp
2010-07-22 15:22 ` Bill Hoffman
2010-07-22 15:49 ` Jeremy Bopp
2010-07-22 19:49 ` Bill Hoffman
2010-07-22 23:48 ` Jeremy Bopp
2010-07-23 1:53 ` Bill Hoffman
2010-07-23 16:28 ` Jeremy Bopp
2010-07-23 17:01 ` git and openssh issue (eblake?) Christopher Faylor
2010-08-02 14:08 ` Bill Hoffman [this message]
2010-08-12 13:46 ` Bill Hoffman
2010-10-03 2:54 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C56D167.2010904@kitware.com \
--to=bill.hoffman@kitware.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).