From: Pierre Habouzit <madcoder@debian.org>
To: spearce@spearce.org
Cc: Git ML <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: regression in 92392b4
Date: Wed, 23 Jul 2008 01:17:45 +0200 [thread overview]
Message-ID: <20080722231745.GD11831@artemis.madism.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2098 bytes --]
Hi, here is a manual painful down-secting (opposed to a bisect ;P) I
did, since git in next cannot fetch on a regular basis for me. The
culprit seems to be commit 92392b4:
┌─(1:11)──<~/dev/scm/git 92392b4...>──
└[artemis] git fetch
remote: Counting objects: 461, done.
remote: Compressing objects: 100% (141/141), done.
remote: Total 263 (delta 227), reused 155 (delta 121)
Receiving objects: 100% (263/263), 95.55 KiB, done.
fatal: Out of memory, malloc failed
fatal: index-pack failed
[2] 16674 abort (core dumped) git fetch
┌─(1:12)──<~/dev/scm/git 92392b4...>──
└[artemis] git checkout -m HEAD~1; make git-index-pack
Previous HEAD position was 92392b4... index-pack: Honor core.deltaBaseCacheLimit when resolving deltas
HEAD is now at 03993e1... index-pack: Track the object_entry that creates each base_data
GIT_VERSION = 1.5.6.3.3.g03993
CC index-pack.o
LINK git-index-pack
┌─(1:12)──<~/dev/scm/git 03993e1...>──
└[artemis] git fetch
remote: Counting objects: 461, done.
remote: Compressing objects: 100% (141/141), done.
remote: Total 263 (delta 227), reused 155 (delta 121)
Receiving objects: 100% (263/263), 95.55 KiB, done.
Resolving deltas: 100% (227/227), completed with 153 local objects.
From git://git.kernel.org/pub/scm/git/git
5ba2c22..0868a30 html -> origin/html
2857e17..abeeabe man -> origin/man
93310a4..95f8ebb master -> origin/master
559998f..e8bf351 next -> origin/next
You can see the commit sha's in the prompt. 03993e1 is fine, 92392b4 is
broken, I've absolutely no clue about what happens.
All I can say is that at some point in get_data_from_pack, obj[1].idx
points to something that is *not* a sha so it's probably corrupted.
(from index-pack.c).
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-07-22 23:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 23:17 Pierre Habouzit [this message]
2008-07-22 23:34 ` regression in 92392b4 Johannes Schindelin
2008-07-23 0:41 ` Shawn O. Pearce
2008-07-23 0:58 ` Johannes Schindelin
2008-07-23 1:09 ` Pierre Habouzit
2008-07-23 1:20 ` Johannes Schindelin
2008-07-22 23:37 ` Pierre Habouzit
2008-07-23 10:14 ` Björn Steinbrink
2008-07-23 10:22 ` Pierre Habouzit
2008-07-23 10:38 ` Pierre Habouzit
2008-07-23 10:49 ` Johannes Schindelin
2008-07-23 10:56 ` Björn Steinbrink
2008-07-23 11:19 ` Pierre Habouzit
2008-07-23 11:37 ` Johannes Schindelin
2008-07-23 11:50 ` Pierre Habouzit
2008-07-23 12:00 ` Björn Steinbrink
2008-07-23 12:11 ` [PATCH] index-pack: never prune base_cache Pierre Habouzit
2008-07-23 12:52 ` Björn Steinbrink
2008-07-23 13:09 ` Johannes Schindelin
2008-07-23 13:20 ` Pierre Habouzit
2008-07-23 13:46 ` Johannes Schindelin
2008-07-23 13:44 ` Björn Steinbrink
2008-07-23 14:41 ` Johannes Schindelin
2008-07-23 15:30 ` Pierre Habouzit
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=20080722231745.GD11831@artemis.madism.org \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
/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