From: Taylor Blau <me@ttaylorr.com>
To: Son Luong Ngoc <sluongng@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>, git <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: Seg Fault on git fetch with fetch.negotiationAlgorithm=skipping
Date: Fri, 1 May 2020 16:13:32 -0600 [thread overview]
Message-ID: <20200501221332.GB41612@syl.local> (raw)
In-Reply-To: <BFB84B3B-FB39-4217-A6C6-7599F6F755E2@gmail.com>
On Fri, May 01, 2020 at 10:13:43AM +0200, Son Luong Ngoc wrote:
> Hi Taylor,
>
> > On Apr 30, 2020, at 22:20, Taylor Blau <me@ttaylorr.com> wrote:
> >
> > Are you able to share a core file? If not, it would be very helpful for
> > you to 'git fast-export --anonymize ...' and see if you can reproduce
> > the problem on an anonymized copy of your repository.
>
> I played a bit with --anonymized yesterday but export/import is slow and I still need to review
> the history to see whether it could be released.
>
> It might take more time than just a few days.
That's OK. Please let us know when you have it by responding in the
sub-thread here, and I will be happy to take a look.
> > I can speculate about the cause of the crash from your strace above, but
> > a core file would be more helpful.
>
> I have added perf trace2 in https://gist.github.com/sluongng/e48327cc911c617ed2ef8578acc2ea34#file-perf-trace2-L52
> (git version is 2.26.2)
>
> I think this trace is a lot cleared than the strace log.
>
> > Thanks,
> > Taylor
>
> Cheers,
> Son Luong.
Thanks,
Taylor
prev parent reply other threads:[~2020-05-01 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 14:55 Seg Fault on git fetch with fetch.negotiationAlgorithm=skipping Son Luong Ngoc
2020-04-30 20:20 ` Taylor Blau
2020-05-01 8:13 ` Son Luong Ngoc
2020-05-01 22:13 ` Taylor Blau [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200501221332.GB41612@syl.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sluongng@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).