git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: git@vger.kernel.org
Subject: Re: something broken just now on git-pull from openbsd to OSX
Date: Fri, 18 Aug 2006 14:26:06 -0700	[thread overview]
Message-ID: <7vwt9568i9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <86hd0ako8h.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "18 Aug 2006 09:22:38 -0700")

merlyn@stonehenge.com (Randal L. Schwartz) writes:

> And even more info:
>
>     $ git-repack -a -d
>     Generating pack...
>     Done counting 2610 objects.
>     Deltifying 2610 objects.
>      100% (2610/2610) done
>     Writing 2610 objects.
>      100% (2610/2610) done
>     Total 2610, written 2610 (delta 1244), reused 2610 (delta 1244)
>     Pack pack-3cd61a256bd8736b13b0356aafff016260c22b80 created.
>     $ git-repack -a -d -f
>     Generating pack...
>     Done counting 2610 objects.
>     Deltifying 2610 objects.
>     Segmentation fault 
>
> Oops!  That's not good.

Indeed it is not good.

First we would need to see who is dying.

git-repack -a -d -f does:

 - list all the objects that need to be packed by running

	git rev-list --objects --all

 - piping that to pack-objects

 - after that remove old ones (because -d is given)

I am suspecting it is either rev-list or pack-objects, but let's
isolate which first.

	git-rev-list --objects --all >/var/tmp/revlist.out

Does this die?  If not

	git-pack-objects pack </var/tmp/revlist.out

does this die?

Once you isolate which, can you bisect to see where it broke in
recent history (assuming it worked ever on OSX)?

      reply	other threads:[~2006-08-18 21:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 16:17 something broken just now on git-pull from openbsd to OSX Randal L. Schwartz
2006-08-18 16:19 ` Randal L. Schwartz
2006-08-18 16:22   ` Randal L. Schwartz
2006-08-18 21:26     ` Junio C Hamano [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=7vwt9568i9.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.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 NNTP newsgroup(s).