From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: git@vger.kernel.org
Subject: git bundle verify segfaults
Date: Fri, 24 May 2019 13:48:35 -0400 [thread overview]
Message-ID: <20190524174835.GA2068@chatter.i7.local> (raw)
Hello:
I seem to be getting a segfault trying to verify bundles created from
linux.git. It's easy to reproduce:
$ cd linux
$ git show-ref master
c50bbf615f2f0028ad1771506ef8807130ccc2ce refs/heads/master
$ git bundle create /tmp/linux.bundle master
Enumerating objects: 6705678, done.
Counting objects: 100% (6705678/6705678), done.
Delta compression using up to 8 threads
Compressing objects: 100% (1037089/1037089), done.
Writing objects: 100% (6705678/6705678), 1.19 GiB | 97.81 MiB/s, done.
Total 6705678 (delta 5657955), reused 6664576 (delta 5622679)
$ cd /tmp
$ git bundle verify linux.bundle
BUG: refs.c:1750: attempting to get main_ref_store outside of repository
Aborted (core dumped)
$ git --version
git version 2.21.0
Best,
-K
next reply other threads:[~2019-05-24 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 17:48 Konstantin Ryabitsev [this message]
2019-05-24 18:49 ` git bundle verify segfaults SZEDER Gábor
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=20190524174835.GA2068@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).