All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git-update-server-info crashes on hera.kernel.org:/pub/scm/libs/klibc/klibc.git
Date: Sat, 03 Dec 2005 23:12:02 -0800	[thread overview]
Message-ID: <439296C2.8020809@zytor.com> (raw)
In-Reply-To: <7v64q5tkhi.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> "H. Peter Anvin" <hpa@zytor.com> writes:
> 
> 
>>FWIW, I invoked this as:
>>
>>hpa@hera:~(0)$ GIT_DIR=/pub/scm/libs/klibc/klibc.git git-update-server-info
>>Segmentation fault
> 
> 
> Trusting that I *won't* be able to write into that repository, I
> tried to run that and after getting an error ("cannot update
> info/refs file", which I wanted to see) I seem to be getting the
> same segfault.  GDB session reveals the binary is heavily
> optimized or inlined, so it is hard to see what it is doing
> though.
> 
> But there is one thing that is mysterious about your repository,
> and by mirroring that peculiarity with the copy in my home
> directory, I managed to reproduce the problem with my copy.  Why
> does the objects/info/alternates in that repository point at
> itself?  I suspect if you remove that file you will be OK.
> 
> update-server-info simply dying, instead of complaining about
> it, is a bug nevertheless, and removal of the
> unnecessary/possibly wrong alternate is only a workaround, but I
> hope that would unblock you in the meantime..
> 

Removing that file did indeed work.  I have no idea where it comes from, 
though; although I would guess it comes from another repository that I 
merged with (which had my original repository set as an alternate.)

	-hpa

      reply	other threads:[~2005-12-04  7:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-03 22:35 git-update-server-info crashes on hera.kernel.org:/pub/scm/libs/klibc/klibc.git H. Peter Anvin
2005-12-04  6:16 ` Junio C Hamano
2005-12-04  6:27   ` H. Peter Anvin
2005-12-04  7:00     ` Junio C Hamano
2005-12-04  7:12       ` H. Peter Anvin [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=439296C2.8020809@zytor.com \
    --to=hpa@zytor.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.