From: Robert Wruck <wruck@tweerlei.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, Peter Baumann <waste.manager@gmx.de>,
git@vger.kernel.org
Subject: Re: [BUG] git cat-file does not terminate
Date: Wed, 09 Mar 2011 15:49:41 +0100 [thread overview]
Message-ID: <4D779385.3070602@tweerlei.de> (raw)
In-Reply-To: <7vwrk9cjib.fsf@alter.siamese.dyndns.org>
> I asked (1) if we can find out at runtime if we are on which version of
> cygwin1.dll, and (2) if we can have a small list of "bad" versions of
> cygwin1.dll. If both are true, the runtime test should be trivial, no?
Currently I don't know of a programmatic way to get the cygwin version
except `cygcheck -c cygwin` or `uname -r` but these utilities seem to
know where to find it. I'll take a look at the source.
Unfortunately, the same cygwin version works on most platforms except
WinXP, so its rather a platform issue and I fear that in this case all
cygwin versions up to a currently unknown fixed version will be subject.
Depending on the machine, the "limit" at which write() fails seems to
vary as well. In my initial report, it was about 80MB, on another
machine it was around 200MB...
I submitted a bug report to cygwin over the weekend and tried to debug
what's going on in cygwin1.dll but haven't gone very far yet.
-Robert
next prev parent reply other threads:[~2011-03-09 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 13:04 [BUG] git cat-file does not terminate Robert Wruck
2011-03-04 15:40 ` Peter Baumann
2011-03-04 16:00 ` Jeff King
2011-03-04 17:16 ` Junio C Hamano
2011-03-04 17:29 ` Robert Wruck
2011-03-04 18:26 ` Robert Wruck
2011-03-08 21:14 ` Jeff King
2011-03-08 22:52 ` Junio C Hamano
2011-03-09 14:49 ` Robert Wruck [this message]
2011-03-09 19:32 ` Junio C Hamano
2011-03-09 19:51 ` Robert Wruck
2011-03-09 21:43 ` Jeff King
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=4D779385.3070602@tweerlei.de \
--to=wruck@tweerlei.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=waste.manager@gmx.de \
/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 NNTP newsgroup(s).