From: Nick Hengeveld <nickh@reactrix.com>
To: Mark Wooding <mdw@distorted.org.uk>
Cc: git@vger.kernel.org
Subject: Re: git-http-fetch failure/segfault -- alas no patch
Date: Tue, 31 Jan 2006 09:58:13 -0800 [thread overview]
Message-ID: <20060131175813.GD3873@reactrix.com> (raw)
In-Reply-To: <17374.30792.548889.344768@metalzone.distorted.org.uk>
On Mon, Jan 30, 2006 at 08:34:16PM +0000, Mark Wooding wrote:
> run_active_slot. As far as I can make out, the slot used to collect
> .../info/packs is being /reused/ by fill_active_slots (called by
> step_active_slots) before fetch_indices is returned to.
Good catch, there were a couple of places where slot result data could
be processed after the slot had been reused, with rather unpredictable
results.
There's a patch on the way after a bit more testing.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
prev parent reply other threads:[~2006-01-31 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 20:34 git-http-fetch failure/segfault -- alas no patch Mark Wooding
2006-01-31 9:32 ` Uwe Zeisberger
2006-01-31 11:46 ` Mark Wooding
2006-01-31 17:58 ` Nick Hengeveld [this message]
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=20060131175813.GD3873@reactrix.com \
--to=nickh@reactrix.com \
--cc=git@vger.kernel.org \
--cc=mdw@distorted.org.uk \
/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).